From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Adding srfi-30 comments.
Date: Tue, 03 Sep 2002 13:14:02 -0500 [thread overview]
Message-ID: <87lm6j0wlx.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87wuq3c94w.fsf@zagadka.ping.de> (Marius Vollmer's message of "03 Sep 2002 18:47:59 +0200")
Marius Vollmer <mvo@zagadka.ping.de> writes:
> Would we be compliant if we just extend the existing code that handles
> #! !# to handle #| |# as well? If so, I don't see why we shouldn't do
> it right away.
I'd have to do some testing to be sure. The primary requirements seem
to be:
- #| comments are visible to scheme as a single whitespace
- an error is signaled if a closing is |# not found.
- #| comments can be nested
- R5RS <delimiter> is not extended so tokens, etc. must be separated
from #| comments by a regular R5RS <delimiter>. I presume this
means that you want foo #|bar|#, not foo#|bar|#.
If our #! handling accmodates these requirements, then we're set,
though we might want to specify how #! and #| interact. I'd be likely
to propose:
- a multi-line comment started with #! must end with !#.
- a multi-line comment started with #| must end with |#.
- #! and #| comments may be nested.
and perhaps even
- a #! multi-line comment is only permitted at the start of a scheme
file.
though perhaps there are good reasons not to specify that...
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-09-03 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 5:18 Adding srfi-30 comments Rob Browning
2002-09-03 16:47 ` Marius Vollmer
2002-09-03 16:48 ` Ariel Rios
2002-09-03 18:14 ` Rob Browning [this message]
2002-09-03 18:34 ` Bruce Korb
2002-09-03 18:51 ` Rob Browning
2002-09-03 22:28 ` Maciej Stachowiak
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=87lm6j0wlx.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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).