unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: storm@cua.dk (Kim F. Storm), rms@gnu.org, emacs-devel@gnu.org
Subject: Re: featurep
Date: Tue, 19 Mar 2002 16:20:31 -0500	[thread overview]
Message-ID: <200203192120.g2JLKVQ08387@rum.cs.yale.edu> (raw)
In-Reply-To: m38z8ojr79.fsf@nyaumo.btinternet.com

> storm@cua.dk (Kim F. Storm) writes:
> 
> > However, for a usage point of view, I don't really see why it
> > matters, and IMHO, using featurep will be _less_ intuitive.
> > For example, I think using
> > 
> >   (if (and (make-network-process :feature :family 'local)
> >            (make-network-process :feature :datagram t))
> 
> Having make-network-process doing something other than making a
> network process is not a more intuitive solution than featurep.

Agreed.  I also agree that `featurep' is not a perfect answer, tho.
Ideally, what I'd like is something like

	(featuredp '(make-network-process :family 'local))

where `featuredp' simply takes a function together with a set of
arguments and returns whether or not that call is "supported".
It would first check the fboundness of the function, the number of arguments
and all those things.

But I have no good idea how to go about implementing this thing, so
as a first step, I think that it should be good enough just to make
`make-network-process' fail when called with arguments requiring
unsupported features.  After all, it's generally the case that if
the feature is supported, then we do want to make the function call,
so we might as well call the function and see if it worked.


	Stefan


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  reply	other threads:[~2002-03-19 21:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200203190844.g2J8iOq09224@wijiji.santafe.edu>
2002-03-19 13:39 ` featurep Kim F. Storm
2002-03-19 19:24   ` featurep Jason Rumney
2002-03-19 21:20     ` Stefan Monnier [this message]
2002-03-19 23:09       ` featurep Kim F. Storm
2002-03-19 23:19         ` featurep Stefan Monnier
2002-03-19 23:48           ` featurep Kim F. Storm
2002-03-20  0:03             ` featurep Stefan Monnier
2002-03-19 22:59     ` featurep Kim F. Storm
2002-03-21  9:04     ` featurep Richard Stallman
2002-03-21 13:12       ` featurep Kim F. Storm
2002-03-23  2:35         ` featurep Richard Stallman
2002-03-21 16:44       ` featurep Stefan Monnier
2002-03-21 19:47         ` featurep Kim F. Storm
2002-03-22  0:39           ` featurep Stefan Monnier
2002-03-22  9:14             ` featurep Kim F. Storm

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200203192120.g2JLKVQ08387@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=storm@cua.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).