unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Clinton Ebadi <clinton@unknownlamer.org>
To: "Kjetil S. Matheussen" <k.s.matheussen@notam02.no>
Cc: guile-user@gnu.org
Subject: Re: Me no understand scoping
Date: Wed, 30 Jul 2008 15:03:27 -0400	[thread overview]
Message-ID: <87wsj3b3eo.fsf@unknownlamer.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0807301815320.5097@ttleush> (Kjetil S. Matheussen's message of "Wed\, 30 Jul 2008 18\:18\:50 +0200 \(CEST\)")

"Kjetil S. Matheussen" <k.s.matheussen@notam02.no> writes:

> Clinton Ebadi:
>>
>> As a matter of style, you probably want to avoid local-eval as it will
>> have to be removed whenever Guile ends up with a faster compiler (one
>
> I've never heard this before, and I think you are way wrong.
> first-class environments etc. is what makes Guile special
> and it would be insane to remove it since there are xx other very
> good scheme implementations. No more first-class environments,
> no more Guile for me. Well, I guess someone would fork Guile
> very quick in case it happened though.

Mutable first class environments available at runtime prevent a number
of useful optimizations. Immutable environments at runtime ought to be
fine (with nothing more than some space overhead). 

Mutable environments provided at compile time for macros should be
fine however. I think most everything you'd want to do with an
environment at runtime could be done at compile time instead, and
there is not much convenience lost as you could always recompile a
block to effect a change to its lexical environment.

-- 
And did those feet in ancient times
Walk bare upon these lonely streets like mine?
Does God watch us from that penthouse high above
His children down below who live on air and love?




  reply	other threads:[~2008-07-30 19:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cmu-lmtpd-29005-1217434291-0@mail-imap1.uio.no>
2008-07-30 16:18 ` Me no understand scoping Kjetil S. Matheussen
2008-07-30 19:03   ` Clinton Ebadi [this message]
2008-07-29 21:18 Maciek Godek
2008-07-30  3:24 ` Clinton Ebadi
2008-07-30  8:42   ` Maciek Godek
2008-07-30 14:03     ` Jon Wilson
2008-07-30 15:04       ` Klaus Schilling
2008-07-30 19:24       ` Maciek Godek
2008-07-31  7:20         ` Neil Jerram
2008-07-31 19:21           ` Maciek Godek
2008-07-31 21:37             ` Neil Jerram
2008-07-31 23:07               ` Maciek Godek
2008-08-02 17:43                 ` Neil Jerram
2008-08-02 21:36                   ` Maciek Godek
2008-08-08 20:54                     ` Neil Jerram
2008-08-10 21:49                       ` Maciek Godek
2008-08-09 11:05                     ` Andy Wingo
2008-08-10 22:30                       ` Maciek Godek
2008-09-11 14:56                       ` JonWilson
2008-07-31 23:48             ` Clinton Ebadi
2008-08-01 22:00               ` Maciek Godek
2008-08-02  5:13                 ` Jon Wilson
2008-08-02 21:35                   ` Maciek Godek

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wsj3b3eo.fsf@unknownlamer.org \
    --to=clinton@unknownlamer.org \
    --cc=guile-user@gnu.org \
    --cc=k.s.matheussen@notam02.no \
    /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).