From: Barry Margolin <barmar@alum.mit.edu>
Subject: Re: Mis-features of let
Date: Tue, 19 Apr 2005 08:55:20 -0400 [thread overview]
Message-ID: <barmar-6B8D06.08552019042005@comcast.dca.giganews.com> (raw)
In-Reply-To: 1113892700.139927.168000@g14g2000cwa.googlegroups.com
In article <1113892700.139927.168000@g14g2000cwa.googlegroups.com>,
"rgb" <rbielaws@i1.net> wrote:
> Do you now see what I'm getting at? Only the lifetime of the value
> cell is predictable on a symbol within a let. That makes the other
> cells unsafe to touch because their lifetime is unpredictable.
The lifetimes of the other cells are totally unaffected by the the let,
and nothing in the manual ever suggests that they would be. It doesn't
say they aren't, but it also doesn't say that let doesn't print
anything. Like I said in an earlier post, it's not necessary to list
all the things that an operator doesn't do, since there are an infinite
number of things it doesn't do.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
next prev parent reply other threads:[~2005-04-19 12:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 12:56 Defadvice use Matthias
2005-04-18 17:11 ` rgb
2005-04-18 17:25 ` Johan Bockgård
2005-04-18 19:05 ` rgb
2005-04-18 19:43 ` Stefan Monnier
2005-04-19 0:15 ` rgb
2005-04-19 0:28 ` Stefan Monnier
2005-04-19 3:48 ` Mis-features of let (was Defadvice use) rgb
2005-04-19 4:31 ` Mis-features of let Stefan Monnier
2005-04-19 6:38 ` rgb
2005-04-19 12:21 ` Stefan Monnier
2005-04-19 20:31 ` rgb
2005-04-19 21:45 ` David Kastrup
2005-04-19 12:55 ` Barry Margolin [this message]
2005-04-19 20:31 ` rgb
2005-04-20 4:12 ` Barry Margolin
2005-04-19 21:10 ` rgb
2005-04-19 21:57 ` Kevin Rodgers
2005-04-19 22:00 ` David Kastrup
2005-04-20 1:04 ` rgb
2005-04-20 10:04 ` David Kastrup
2005-04-20 11:57 ` Stefan Monnier
2005-04-20 14:41 ` Thien-Thi Nguyen
2005-04-19 9:41 ` Thien-Thi Nguyen
2005-04-19 5:07 ` Defadvice use Barry Margolin
2005-04-18 17:52 ` Stefan Monnier
2005-04-18 21:07 ` Matthias
2005-04-18 23:20 ` Stefan Monnier
2005-04-18 20:28 ` Kevin Rodgers
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=barmar-6B8D06.08552019042005@comcast.dca.giganews.com \
--to=barmar@alum.mit.edu \
/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).