From: Kevin Ryde <user42@zip.com.au>
To: guile-devel@gnu.org
Subject: Re: Improved (and faster) reader
Date: Sat, 25 Aug 2007 10:45:55 +1000 [thread overview]
Message-ID: <87r6ls1lx8.fsf@zip.com.au> (raw)
In-Reply-To: 87veb6gda2.fsf@chbouib.org
ludo@gnu.org (Ludovic Courtès) writes:
>
> Did you actually trigger it
Yes, it broke the self-tests of my lint program. :) (My program assumed
any pair returned by the reader would have source properties. I've
loosened that, since at least in principle it might not be true of stuff
generated by srfi-10 #,() code, or the like.)
> SCM_COPY_SOURCE_P
By the way, what does that option actually do. The manual just says
"Copy source code expressions", which doesn't leave me any the wiser.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-08-25 0:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 18:21 Further profiling, including howto Andy Wingo
2007-07-22 16:46 ` Improved (and faster) reader Ludovic Courtès
2007-08-11 10:52 ` Ludovic Courtès
2007-08-23 1:08 ` Kevin Ryde
2007-08-23 21:19 ` Ludovic Courtès
2007-08-25 0:45 ` Kevin Ryde [this message]
2007-08-25 8:23 ` Ludovic Courtès
2007-08-25 13:15 ` Andy Wingo
2007-08-26 17:05 ` Ludovic Courtès
2007-09-03 16:59 ` 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=87r6ls1lx8.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).