From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>,
emacs-devel@gnu.org
Subject: Re: featurep
Date: Thu, 21 Mar 2002 19:39:37 -0500 [thread overview]
Message-ID: <200203220039.g2M0dbj19729@rum.cs.yale.edu> (raw)
In-Reply-To: 5x7ko5zosj.fsf@kfs2.cua.dk
> > > Having make-network-process doing something other than making a
> > > network process is not a more intuitive solution than featurep.
> > >
> > > That is exactly what bothers me about it.
> > >
> > > Perhaps we can implement use of lists as subfeatures. Then
> > > (featurep 'make-network-process '(:family local)) could be used
> > > instead of (make-network-process :feature :family 'local).
> >
> > I still haven't heard any evidence that
> >
> > (condition-case nil
> > (make-network-process foo bar baz)
> > (unsupported-networking-feature
> > ...do..something..else...))
> >
> > is not enough and that a separate `featurep' support is required.
>
> One example could be that we need to use different sentinels and
> filters depending on what features are supported. Using the
> featurep method, we only need to define the sentinel and filter
> functions related to the actual method used.
>
> The condition-case approach means that you don't know in advance
> what will be the optimal approach.
I wasn't asking "can you think of a case where `featurep' would
be useful" but "are there such cases". And I don't really care
about cases where `featurep' would be marginally more convenient.
For instance, I'm not convinced by your example: conditionally defining
functions is not something I'd advocate anyway (unless you can put them
in different files, but I doubt the sentinels and filters will
be large enough to warrant my-server-nonblocking.el
and myserver-blocking.el) so have both versions of the code defined
is a perfectly acceptable overhead, just as is the overhead of having
a single version of the functions with a dynamic check inside (I expect
that the different versions of the sentinel and filter codes will
be similar enough that there'll be a fair amount of code-sharing
anyway).
Stefan
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-22 0:39 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 ` featurep Stefan Monnier
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 ` Stefan Monnier [this message]
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=200203220039.g2M0dbj19729@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=emacs-devel@gnu.org \
/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).