From: Marco Maggi <marco.maggi-ipsu@poste.it>
To: bug-guile@gnu.org
Subject: Re: [r6rs] probably bad syntax expansion
Date: Mon, 21 Jun 2010 10:34:51 +0200 [thread overview]
Message-ID: <87wrts3hsk.fsf@rapitore.luna> (raw)
In-Reply-To: 877hls4xu9.fsf@rapitore.luna
"Marco Maggi" wrote:
> Sorry for the self reply; the problem goes away defining
> IDENTIFIER->STRING before its usage. I can understand
> this, but it is not R6RS behaviour. Maybe just
> documenting it as incompatibility is fine.
I take it back. It imposes an order on definitions which
can cause problems in complex libraries (like mine).
--
Marco Maggi
next prev parent reply other threads:[~2010-06-21 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 7:59 [r6rs] probably bad syntax expansion Marco Maggi
2010-06-21 8:02 ` Marco Maggi
2010-06-21 8:34 ` Marco Maggi [this message]
2010-06-21 19:24 ` Andy Wingo
2010-08-08 10:41 ` Andy Wingo
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=87wrts3hsk.fsf@rapitore.luna \
--to=marco.maggi-ipsu@poste.it \
--cc=bug-guile@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).