From: prj@po.cwru.edu (Paul Jarc)
Cc: guile-devel@gnu.org
Subject: Re: srfi-39 implementation
Date: Sat, 08 May 2004 21:09:07 -0400 [thread overview]
Message-ID: <m3hduqh0dy.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <87brky5su3.fsf@zip.com.au> (Kevin Ryde's message of "Sun, 09 May 2004 10:48:04 +1000")
Kevin Ryde <user42@zip.com.au> wrote:
> Jose A Ortega Ruiz <jao@gnu.org> writes:
>> (define get-fluid-tag (lambda () 'get-fluid)) ;; arbitrary unique (as per eq?) value
>
> make-symbol perhaps.
Or (list 0), for minimal memory use (I think).
paul
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-05-09 1:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 1:02 srfi-39 implementation Jose A Ortega Ruiz
2004-05-06 1:24 ` srfi-39 implementation -- Bug fix Jose A Ortega Ruiz
2004-08-15 20:43 ` Marius Vollmer
2004-05-09 0:48 ` srfi-39 implementation Kevin Ryde
2004-05-09 1:09 ` Paul Jarc [this message]
2004-05-10 0:21 ` Jose A. Ortega Ruiz
2004-05-13 21:10 ` Kevin Ryde
2004-05-13 23:23 ` Jose A. Ortega Ruiz
2004-07-19 20:17 ` Marius Vollmer
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=m3hduqh0dy.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--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).