From: Sebastian Tennant <sebyte@smolny.plus.com>
To: guile-user@gnu.org
Subject: Re: Placement of defines
Date: Sat, 27 Dec 2008 15:19:12 +0000 [thread overview]
Message-ID: <wsdlodcf.fsf@vps203.linuxvps.org> (raw)
In-Reply-To: Pine.LNX.4.64-L.0812191807330.7958@padme.ifi.uio.no
Quoth "Kjetil S. Matheussen" <k.s.matheussen@notam02.no>:
>> Sebastian Tennant:
>> guile> ((lambda (x) (set! x "baz\n") (definer 'bar x) (display bar)) "foo\n")
>> baz
>> guile>
>>
>
> Unfortunately, it's not the same. "definer" defines a global variable:
>
> guile> bar
> "baz
> "
Good point. That hadn't occurred to me. Thanks.
Seb
next prev parent reply other threads:[~2008-12-27 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cmu-lmtpd-21674-1229672512-0@mail-imap1.uio.no>
2008-12-19 17:10 ` Placement of defines Kjetil S. Matheussen
2008-12-27 15:19 ` Sebastian Tennant [this message]
[not found] <cmu-lmtpd-18264-1229620135-1@mail-imap1.uio.no>
2008-12-18 17:31 ` Kjetil S. Matheussen
2008-12-18 18:47 ` Sebastian Tennant
2008-12-18 20:57 ` Ludovic Courtès
2008-12-19 11:18 ` Sebastian Tennant
2008-12-18 17:00 Sebastian Tennant
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=wsdlodcf.fsf@vps203.linuxvps.org \
--to=sebyte@smolny.plus.com \
--cc=guile-user@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).