From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org
Subject: Re: Adding srfi-30 comments.
Date: 03 Sep 2002 18:47:59 +0200 [thread overview]
Message-ID: <87wuq3c94w.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87admz3b3f.fsf@raven.i.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> Srfi-30's in final status,
>
> http://srfi.schemers.org/srfi-30/srfi-30.html
>
> so probably worth considering. Should we just add support for this
> and enable it by default?
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.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
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 16:47 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 [this message]
2002-09-03 16:48 ` Ariel Rios
2002-09-03 18:14 ` Rob Browning
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=87wuq3c94w.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--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).