unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Kjetil S. Matheussen" <k.s.matheussen@notam02.no>
To: guile-user@gnu.org
Cc: ludo@gnu.org
Subject: Re: Injecting variables into closures.
Date: Thu, 29 Nov 2007 19:43:13 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0711291935070.9048@ttleush> (raw)
In-Reply-To: <cmu-lmtpd-10256-1196356001-0@mail-imap2.uio.no>


Ludovic Court?s:
>
> Hi,
>
> "Kjetil S. Matheussen" <k.s.matheussen@notam02.no> writes:
>
>> Now I wonder, is this safe and portable? Or are there
>> other and better ways to do this?
>
> Neither `define-macro' nor `procedure->macro' is portable: both are
> Guile-specific (SCM may have similar forms, though).
>

Thanks, but by "portable", I did (of course) mean portable
across various versions of Guile, not any of the scheme
standards...


> Another, simpler, Guile-specific way to do this would be:
>
>  (module-define! (current-module) 'gakk 'some-value)
>

Thanks, but that's probably not enough for what I
want to do. I need to simulate dynamic scoping
somehow, and I think its only possible to do that
by manipulating the environment. But I'm not
going to do that if its going to break with
forthcoming releases of Guile.



_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


       reply	other threads:[~2007-11-29 18:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cmu-lmtpd-10256-1196356001-0@mail-imap2.uio.no>
2007-11-29 18:43 ` Kjetil S. Matheussen [this message]
2007-11-29 14:04 Injecting variables into closures Kjetil S. Matheussen
2007-11-29 14:44 ` Kjetil S. Matheussen
2007-11-29 14:54 ` Kjetil S. Matheussen
2007-11-29 16:02   ` Ludovic Courtès
     [not found] ` <877ik1dpyj.fsf@unknownlamer.org>
2007-11-29 15:52   ` Kjetil S. Matheussen
2007-11-29 15:53 ` Ludovic Courtès

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=Pine.LNX.4.64.0711291935070.9048@ttleush \
    --to=k.s.matheussen@notam02.no \
    --cc=guile-user@gnu.org \
    --cc=ludo@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).