unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Daniel Skarda <0rfelyus@ucw.cz>
Subject: Re: srfi-26
Date: Sun, 29 Feb 2004 11:04:04 +0100	[thread overview]
Message-ID: <m0hdxa8anf.fsf@hobitin.ucw.cz> (raw)
In-Reply-To: <87vflrc65w.fsf@zip.com.au> (Kevin Ryde's message of "Sun, 29 Feb 2004 06:15:07 +1000")


>> 	   (let ((var (gensym)))
>
> Would make-symbol be a goer here, instead of gensym?

  1) gensym is a standard (Common Lisp) for introducing new symbols in
     defmacros.
 
  2) I am not too familiar with Guile internals, I do not know too much
     about interned/uninterned symbols. I wrote cut/cute using Guile 1.6.
     AFAIR make-symbol was introduced in 1.7

  3) gensym is better for macro debugging (when you use macroexpand +
     pretty-print, #<uninterned symbol foo 807f810> is long and quite
     annoying to read) 

  4) Does make-symbol any significant performance improvement over plain
     gensyms?

0.



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2004-02-29 10:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15  2:17 srfi-26 Alex Shinn
2004-01-15  9:36 ` srfi-26 Daniel Skarda
2004-01-21  0:44   ` srfi-26 Marius Vollmer
2004-01-23  0:44     ` srfi-26 Kevin Ryde
2004-01-24 10:22       ` srfi-26 Daniel Skarda
2004-02-28 20:15   ` srfi-26 Kevin Ryde
2004-02-29 10:04     ` Daniel Skarda [this message]
2004-03-01 21:10       ` srfi-26 Kevin Ryde
2004-01-15 22:08 ` srfi-26 Kevin Ryde
2004-01-16  3:28   ` srfi-26 Alex Shinn
2004-01-16  4:13     ` srfi-26 Paul Jarc
2004-01-16 18:53       ` srfi-26 Greg Troxel
2004-01-19  8:22         ` srfi-26 Alex Shinn
2004-01-19 16:43           ` srfi-26 Stephen Compall

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=m0hdxa8anf.fsf@hobitin.ucw.cz \
    --to=0rfelyus@ucw.cz \
    /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).