From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: sds@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: 24.3.50; Use of deprecated ((lambda ...) ...) form
Date: Fri, 09 Nov 2012 10:59:36 -0500 [thread overview]
Message-ID: <jwvy5ia4vn3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87390ieug9.fsf@gnu.org> (Sam Steingold's message of "Fri, 09 Nov 2012 09:12:38 -0500")
[ Please use M-x report-emacs-bug (or send it to
bug-gnu-emacs@gnu.org). ]
> byte compilation now warns
> .emacs.el:46:39:Warning: Use of deprecated ((lambda ...) ...) form
> .emacs.el:46:39:Warning: Use of deprecated ((lambda ...) ...) form
> .emacs.el:46:39:Warning: Use of deprecated ((lambda ...) ...) form
> .emacs.el:46:39:Warning: Use of deprecated ((lambda ...) ...) form
> .emacs.el:1255:20:Warning: Use of deprecated ((lambda ...) ...) form
> .emacs.el:1259:43:Warning: Use of deprecated ((lambda ...) ...) form
> for forms like
> (eval-and-compile (defvar ...))
Oh, sorry I forgot one hunk. Should be fixed now.
> why is ((lambda ...) ...) deprecated?
Why not?
> this is one of the oldest lisp constructs!
Old doesn't make it good. If you want to bind local variables, you know
where to find `let', don't you?
> If it is to be deprecated, then the macros above must be modified so
> that their compilation does not warn.
Actually, the problem was much deeper than in those macros. But yes, it
needs to be fixed.
Stefan
next prev parent reply other threads:[~2012-11-09 15:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 14:12 24.3.50; Use of deprecated ((lambda ...) ...) form Sam Steingold
2012-11-09 15:59 ` Stefan Monnier [this message]
2012-11-09 16:15 ` Paul Eggert
2012-11-09 16:38 ` Sam Steingold
2012-11-09 17:05 ` Glenn Morris
2012-11-09 19:22 ` Sam Steingold
2012-11-09 16:50 ` Drew Adams
2012-11-09 17:54 ` Stefan Monnier
2012-11-09 19:43 ` Sam Steingold
-- strict thread matches above, loose matches on Subject: below --
2012-11-10 0:05 Barry OReilly
2012-11-10 1:59 ` Stefan Monnier
2012-11-10 7:16 ` Stephen J. Turnbull
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=jwvy5ia4vn3.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=sds@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).