From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Are there any problems with lexical-let or other cl-macros???
Date: Tue, 20 Jul 2010 00:44:07 +0200 [thread overview]
Message-ID: <jwvr5izytwc.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: fb418749-65c8-460a-bdd6-a354b1940f68@u26g2000yqu.googlegroups.com
>> What I don't understand is that simply replacing let with lexical-let
>> will solve the problem.
> To be more precise, it would exchange such a problem with a memory
> leak problem (`lexical-let' leaks memory).
In which sense does lexical-let leak memory?
Stefan
next prev parent reply other threads:[~2010-07-19 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 13:01 Are there any problems with lexical-let or other cl-macros??? LanX
2010-06-01 13:18 ` Pascal J. Bourguignon
2010-06-01 14:20 ` LanX
2010-06-01 15:45 ` Helmut Eller
2010-06-01 15:58 ` LanX
2010-06-01 16:24 ` Helmut Eller
2010-06-02 11:26 ` Pascal J. Bourguignon
2010-07-15 0:13 ` Elena
2010-07-19 22:44 ` Stefan Monnier [this message]
2010-07-20 7:56 ` Elena
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=jwvr5izytwc.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).