all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: Always using let*
Date: Mon, 15 Sep 2014 09:14:46 -0400	[thread overview]
Message-ID: <barmar-E51F0B.09144615092014@news.eternal-september.org> (raw)
In-Reply-To: 87mwa1lhb1.fsf@kuiper.lan.informatimago.com

In article <87mwa1lhb1.fsf@kuiper.lan.informatimago.com>,
 "Pascal J. Bourguignon" <pjb@informatimago.com> wrote:

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
> 
> >> Lisps such as Common Lisp were specifically designed with this
> >> parallel evaluation in mind.  The spec (and CLTL(2)) specifically
> >> emphasizes the inherent parallelism (independence) here that
> >> implies the *possibility* of parallel evaluation.
> >
> > I simply claim that this is bogus.  Only the var-binding is "parallel", not
> > the computation of each value.  So it's a "parallel binding" semantics,
> > but it has nothing to do with efficient execution on multiple
> > execution units.
> 
> The claim is not bogus.  It's just that in general, in presence of side
> effects, since the expressions must be evaluated from left to right,
> indeed, only the assignments can be performed in parallel.

If the LET can be done in parallel, so could LET*. Remember, we're 
talking about compiled code. The inner and outer variables are not the 
same memory location, even if they have the same name. The difference 
between LET and LET* just has to do with which scope the compiler looks 
up the name in.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***


      parent reply	other threads:[~2014-09-15 13:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-14 19:46 Always using let* Cecil Westerhof
2014-09-14 21:25 ` Drew Adams
2014-09-15 16:15   ` Drew Adams
     [not found]   ` <mailman.8924.1410797740.1147.help-gnu-emacs@gnu.org>
2014-09-15 18:01     ` Cecil Westerhof
2014-09-15 22:20       ` Emanuel Berg
2014-09-16 12:05         ` Cecil Westerhof
2014-09-16 22:40           ` Emanuel Berg
2014-09-18 17:02             ` Cecil Westerhof
2014-09-18 21:05               ` Emanuel Berg
2014-09-16 14:23     ` sokobania.01
2014-09-16 16:41       ` Drew Adams
2014-09-16 20:49       ` Stefan Monnier
2014-09-16 22:45       ` Emanuel Berg
     [not found]       ` <mailman.8998.1410901776.1147.help-gnu-emacs@gnu.org>
2014-09-16 22:48         ` Emanuel Berg
2014-09-17  1:09           ` Stefan Monnier
2014-09-17  1:18             ` Emanuel Berg
2014-09-14 21:40 ` Joe Fineman
     [not found] ` <mailman.8868.1410729956.1147.help-gnu-emacs@gnu.org>
2014-09-14 21:41   ` Emanuel Berg
2014-09-14 22:11   ` Cecil Westerhof
2014-09-14 22:56     ` Drew Adams
2014-09-14 22:41   ` Stefan Monnier
2014-09-14 23:06     ` Drew Adams
     [not found]     ` <mailman.8871.1410736002.1147.help-gnu-emacs@gnu.org>
2014-09-15  0:47       ` Emanuel Berg
2014-09-15  2:12         ` Pascal J. Bourguignon
2014-09-15  2:22       ` Stefan Monnier
2014-09-15  2:59         ` Pascal J. Bourguignon
2014-09-15 12:31           ` Stefan Monnier
2014-09-15 16:15             ` Drew Adams
2014-09-15 19:05               ` Stefan Monnier
     [not found]               ` <mailman.8930.1410808006.1147.help-gnu-emacs@gnu.org>
2014-09-15 22:28                 ` Emanuel Berg
2014-09-16  0:38                   ` Pascal J. Bourguignon
2014-09-15 13:14           ` Barry Margolin [this message]

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=barmar-E51F0B.09144615092014@news.eternal-september.org \
    --to=barmar@alum.mit.edu \
    --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.
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.