From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: pushed to master: extensibility to (ice-9 session)
Date: Wed, 28 Jan 2009 09:31:56 +0100 [thread overview]
Message-ID: <87d4e7kf0j.fsf@gnu.org> (raw)
In-Reply-To: 87iqo0uv5b.fsf@unknownlamer.org
Hi,
Clinton Ebadi <clinton@unknownlamer.org> writes:
> *FOO* to me implies that it is a fluid (as the *FOO* tradition comes
> from Common Lisp where it is used to mark dynamically scoped
> variables).
I had that feeling, too (although I never wrote a line of CL), and I
follow this convention in my Scheme projects, but I see that at least
Bigloo uses that convention for globals. Scheme48 people seem to like
using `&'-prefixed names, as in SRFI-35 and parts of R6RS. So Neil is
probably right in saying there's no convention. ;-)
Ludo'.
next prev parent reply other threads:[~2009-01-28 8:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 12:50 pushed to master: extensibility to (ice-9 session) Andy Wingo
2009-01-27 20:30 ` Ludovic Courtès
2009-01-27 22:02 ` Neil Jerram
2009-01-27 23:31 ` Ludovic Courtès
2009-01-28 0:33 ` Clinton Ebadi
2009-01-28 8:31 ` Ludovic Courtès [this message]
2009-01-28 10:29 ` Andy Wingo
2009-01-28 12:26 ` Ludovic Courtès
2009-01-28 15:03 ` Andy Wingo
2009-01-27 22:10 ` Neil Jerram
2009-01-28 11:16 ` Andy Wingo
2009-02-03 23:25 ` Neil Jerram
2009-02-04 8:13 ` szgyg
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=87d4e7kf0j.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).