From: Dmitri Paduchikh <dpaduchikh@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Lexical byte-compilation warnings cleanup
Date: Thu, 22 Aug 2013 11:05:07 +0600 [thread overview]
Message-ID: <8761uypb7g.fsf@dpaduchikh.invalid> (raw)
In-Reply-To: <CAFM41H3Q7Yq08pQQMQHb5t2o4E4e-E7sd9Z+aDp=zJcWPDFFww@mail.gmail.com> (Barry OReilly's message of "Wed, 21 Aug 2013 19:12:52 -0400")
Barry OReilly wrote:
>>> The warning seems to say opposite:
>> Yup. The way I thought about it when I wrote it is that `load-path'
>> is a dynamically-scoped var, not a lexical var. But indeed, here it
>> will (locally) be a lexical var, so the wording is rather poor.
>>
>> Suggestions for better wording?
> How about:
> Warning: Lexically bound argument %s is already defined as dynamically
> bound
IMO, this does not explain what happens actually. I would rather prefer
such variant:
Warning: Lexically bound argument shadows dynamic variable %s
--
With best regards
Dmitri Paduchikh
next prev parent reply other threads:[~2013-08-22 5:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 23:12 Lexical byte-compilation warnings cleanup Barry OReilly
2013-08-22 5:05 ` Dmitri Paduchikh [this message]
2013-08-22 20:41 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2013-08-19 23:33 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
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8761uypb7g.fsf@dpaduchikh.invalid \
--to=dpaduchikh@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.