From: Miles Bader <miles@gnu.org>
Cc: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>,
emacs-devel@gnu.org
Subject: Re: locate-file in Emacs
Date: 19 Apr 2002 00:31:38 +0900 [thread overview]
Message-ID: <87k7r558h1.fsf@tc-1-100.kawasaki.gol.ne.jp> (raw)
In-Reply-To: <sxs1yddavob.fsf@florida.arsdigita.de>
Hrvoje Niksic <hniksic@arsdigita.com> writes:
> > you should be able to keep backward compatibility just fine.
> > The qusetion is whether or not you find the `predicate' interface
> > preferable.
>
> I find this "mixing" of interfaces far from elegant, but I'll agree
> that it's flexible. If that's your price of keeping a unified
> interface, I'll accept. But I'd prefer to just keep MODE.
I think that probably the best thing to do is to simply deprecate the
MODE interface in documentation and recommend using a predicate in both
emacs and xemacs. So think of it as an interface _change_, but with
backward compatibility (similar to the previous interface change you
apparently made).
My reasoning:
* Clearly a predicate is more powerful, and could completely replace
the MODE interface if it weren't for backward compatibility concerns.
* According to Stefan's earlier post, he couldn't find any code that
actually used any value for MODE except `executable', so the
potential programmer-convenience benefit of the MODE interface
doesn't appear to be much of an issue
[e.g. being able to say '(writable executable) instead of
(lambda (f) (or (file-writable-p f) (file-executable-p f))) ]
* Using a predicate is more elegant, and more `lispy'.
I understand that it's annoying to make yet another interface to the
same function, but this one is pretty innocuous.
-Miles
--
Quidquid latine dictum sit, altum viditur.
next prev parent reply other threads:[~2002-04-18 15:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 5:05 locate-file in Emacs Hrvoje Niksic
2002-04-17 5:47 ` Eli Zaretskii
2002-04-17 8:53 ` Hrvoje Niksic
2002-04-17 9:28 ` Stefan Monnier
2002-04-17 9:47 ` Hrvoje Niksic
2002-04-17 10:01 ` Stefan Monnier
2002-04-18 13:16 ` Hrvoje Niksic
2002-04-18 13:54 ` Miles Bader
2002-04-18 14:09 ` Hrvoje Niksic
2002-04-18 14:25 ` Miles Bader
2002-04-18 14:08 ` Stefan Monnier
2002-04-18 15:11 ` Hrvoje Niksic
2002-04-18 15:27 ` Stefan Monnier
2002-04-18 16:20 ` Hrvoje Niksic
2002-04-18 18:59 ` Stefan Monnier
2002-04-25 12:12 ` Hrvoje Niksic
2002-04-25 22:52 ` Stefan Monnier
2002-05-06 15:58 ` Hrvoje Niksic
[not found] ` <200205061655.g46Gt3K01382@rum.cs.yale.edu>
2002-05-06 19:53 ` Hrvoje Niksic
[not found] ` <200205062052.g46KqwO02482@rum.cs.yale.edu>
2002-05-06 20:59 ` Hrvoje Niksic
2002-05-06 21:12 ` Stefan Monnier
2002-05-06 21:57 ` Hrvoje Niksic
2002-05-07 20:06 ` Richard Stallman
2002-04-18 16:39 ` Eli Zaretskii
2002-04-18 16:24 ` Hrvoje Niksic
2002-04-19 5:25 ` Richard Stallman
2002-04-18 15:31 ` Miles Bader [this message]
2002-04-18 16:29 ` Hrvoje Niksic
2002-04-18 16:45 ` Miles Bader
2002-04-18 16:49 ` Hrvoje Niksic
2002-04-18 16:54 ` Miles Bader
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=87k7r558h1.fsf@tc-1-100.kawasaki.gol.ne.jp \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
/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).