From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Drew Adams <drew.adams@oracle.com>
Cc: 411@debbugs.gnu.org
Subject: bug#411: 23.0.60; flet and byte-compilation
Date: Wed, 31 Oct 2012 12:06:39 -0400 [thread overview]
Message-ID: <jwv7gq68wbz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <6D4A84ADD22044839626ADB099FD2F4C@us.oracle.com>
>> Indeed, because `cl-flet' is a different beast, much more
>> like `labels' than like CL's `flet' (it is lexically scoped).
> Just out of curiosity (and I haven't followed this thread), why?
Because:
- CL's `flet' is completely unlike Common-Lisp's `flet'.
- CL's `flet' is more like defadvice, except (dynamically) scoped and
without adjusting the docstring to at least mention that something
fishy is going on.
IOW because CL's `flet' does something we generally want to discourage.
Or rather, because CL's `flet' was a mistake, hence its being
marked obsolete.
> Or call this `foobar' or whatever. Calling it `cl-flet' seems the more
> misleading the farther the behavior gets from CL's `flet' - no?
`cl-flet' is a (hopefully) faithful implementation of Common-Lisp's
`flet', so I think it deserves its name.
Stefan
next prev parent reply other threads:[~2012-10-31 16:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 2:16 bug#411: 23.0.60; flet and byte-compilation Chong Yidong
2008-09-25 17:45 ` Richard M. Stallman
2008-09-26 18:48 ` Glenn Morris
2008-10-20 1:05 ` Glenn Morris
2008-10-23 2:41 ` Glenn Morris
2008-10-23 2:50 ` Processed: " Emacs bug Tracking System
2012-10-31 3:56 ` Glenn Morris
2012-10-31 13:58 ` Stefan Monnier
2012-10-31 15:01 ` Drew Adams
2012-10-31 16:06 ` Stefan Monnier [this message]
2012-10-31 16:13 ` Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2008-09-15 8:04 Glenn Morris
2008-06-14 15:17 Michael Heerdegen
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=jwv7gq68wbz.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=411@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).