From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: Gnus compatibility with the lexical binding branch
Date: Fri, 08 Apr 2011 00:51:08 -0500 [thread overview]
Message-ID: <87bp0h70kz.fsf@lifelogs.com> (raw)
In-Reply-To: <jwv8vvx784u.fsf-monnier+INBOX@gnu.org>
On Tue, 29 Mar 2011 20:42:20 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> Is there an example of how to do this properly, how to test that it's
>> correct, and is there any way to catch it at the byte-compile stage?
SM> Example, no, and neither "tests that it's correct", but the Texinfo doc
SM> includes a discussion of how to do it (using byte-compiler messages to
SM> catch likely problems).
I looked at (info "(elisp) Lexical Binding") and
(info "(elisp) Converting to Lexical Binding") and it was educational,
though a few examples would have been nice to explain how it all works,
especially what the resulting `closure' cons cell looks like. Would you
like me to write something up?
(info "(elisp) Extent") incorrectly says that Emacs Lisp does not have
closures so it probably should be fixed. I don't know the details well
enough to offer a patch.
Ted
next prev parent reply other threads:[~2011-04-08 5:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 10:11 Gnus bugfixing is broken David Kastrup
2011-03-14 14:47 ` Lars Magne Ingebrigtsen
2011-03-14 15:17 ` David Kastrup
2011-03-14 16:12 ` Adam Sjøgren
2011-03-14 17:47 ` Sivaram Neelakantan
2011-03-14 16:22 ` Lars Magne Ingebrigtsen
2011-03-14 19:13 ` message-yank-original issue (was: Gnus bugfixing is broken.) Ted Zlatanov
2011-03-14 19:38 ` message-yank-original issue Antoine Levitt
2011-03-14 19:47 ` Ted Zlatanov
2011-03-14 21:02 ` Antoine Levitt
2011-03-14 22:04 ` Ted Zlatanov
2011-03-15 0:36 ` Michael Welsh Duggan
2011-03-15 15:30 ` Lars Magne Ingebrigtsen
2011-03-15 15:29 ` Lars Magne Ingebrigtsen
2011-03-15 15:49 ` Ted Zlatanov
2011-03-15 15:56 ` Lars Magne Ingebrigtsen
2011-03-15 9:34 ` Ted Zlatanov
2011-03-15 9:48 ` David Kastrup
2011-03-15 10:01 ` Ted Zlatanov
2011-03-26 19:34 ` Sven Joachim
2011-03-28 19:05 ` Ted Zlatanov
2011-03-28 19:57 ` Sven Joachim
2011-03-28 20:06 ` Ted Zlatanov
2011-03-28 20:35 ` Stefan Monnier
2011-03-29 5:37 ` Antoine Levitt
2011-03-28 20:41 ` Stefan Monnier
2011-03-29 14:55 ` Ted Zlatanov
2011-03-29 15:08 ` David Kastrup
2011-03-29 15:20 ` Gnus compatibility with the lexical binding branch (was: message-yank-original issue) Ted Zlatanov
2011-03-29 20:16 ` Gnus compatibility with the lexical binding branch Stefan Monnier
2011-03-29 20:53 ` Ted Zlatanov
2011-03-30 0:42 ` Stefan Monnier
2011-04-08 5:51 ` Ted Zlatanov [this message]
2011-03-15 10:06 ` Gnus bugfixing is broken Ted Zlatanov
2011-03-15 13:31 ` Didier Verna
2011-03-15 13:52 ` Ted Zlatanov
2011-03-15 15:23 ` Lars Magne Ingebrigtsen
2011-03-15 15:56 ` Ted Zlatanov
2011-03-15 16:09 ` Lars Magne Ingebrigtsen
2011-03-15 17:01 ` Didier Verna
2011-03-15 13:58 ` Michael Albinus
2011-03-15 14:46 ` Didier Verna
2011-03-15 14:57 ` Ted Zlatanov
2011-03-15 15:08 ` Michael Albinus
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=87bp0h70kz.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--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.
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 NNTP newsgroup(s).