From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Daniel Hackney <dan@haxney.org>,
Emacs development discussions <emacs-devel@gnu.org>
Subject: RE: Lexical byte-compilation warnings cleanup
Date: Tue, 20 Aug 2013 17:10:04 -0700 (PDT) [thread overview]
Message-ID: <6daf4da3-1d3a-4f4c-9db8-7174fb6da584@default> (raw)
In-Reply-To: <jwvob8s7xyy.fsf-monnier+emacs@gnu.org>
> >> Indeed, it does not refer to the dynamically bound variable.
> > Why is that? Will this be fixed, or is this the intended design?
^^^^^^^^^^^^
>
> Intended design.
And the intention is? The design is? The reason is?
> > Even if things are currently a work in progress, is that the direction
> > you intend to head, or are you aiming elsewhere?
>
> I have never aimed to do what CL does. As language designers, we just
> take idea from here and there.
>
> Elisp's design is different from CL's design partly for historical
> reasons but also for technical reasons: Elisp needs to be interpretable
> efficiently, for example.
OK, and how does the need for efficient interpretation enter into the
design decision that a function parameter whose name is the same as a
dynamically scoped variable is "not allowed" or does not refer to that
variable?
next prev parent reply other threads:[~2013-08-21 0:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 23:33 Lexical byte-compilation warnings cleanup Daniel Hackney
2013-08-20 0:01 ` Juanma Barranquero
2013-08-20 0:11 ` Glenn Morris
2013-08-20 5:47 ` Stefan Monnier
2013-08-20 15:25 ` Drew Adams
2013-08-20 20:41 ` Stefan Monnier
2013-08-20 21:31 ` Drew Adams
2013-08-20 23:21 ` Stefan Monnier
2013-08-21 0:10 ` Drew Adams [this message]
2013-08-21 1:53 ` Stephen J. Turnbull
2013-08-21 2:57 ` Drew Adams
2013-08-21 4:49 ` Stefan Monnier
2013-09-04 20:50 ` Daniel Hackney
2013-09-15 19:33 ` Daniel Colascione
2013-08-21 5:19 ` Dmitri Paduchikh
2013-08-21 20:12 ` Stefan Monnier
2013-09-05 3:30 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2013-08-21 23:12 Barry OReilly
2013-08-22 5:05 ` Dmitri Paduchikh
2013-08-22 20:41 ` Stefan Monnier
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=6daf4da3-1d3a-4f4c-9db8-7174fb6da584@default \
--to=drew.adams@oracle.com \
--cc=dan@haxney.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).