From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: doco srfi-13 string-replace
Date: 02 Jun 2003 17:58:39 +0200 [thread overview]
Message-ID: <87u1b8a2ts.fsf@zagadka.ping.de> (raw)
In-Reply-To: <20030602082344.GA925@patroclus>
Martin Grabmueller <magr@cs.tu-berlin.de> writes:
> It would be best to adjust the code to match the final SRFI, instead
> of introducing extensions.
Hmm, how long has our code being out there already? When it has been
shipped with Guile 1.6, we need to be very conservative about changing
things that are not outright bugs.
--
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:[~2003-06-02 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 21:33 doco srfi-13 string-replace Kevin Ryde
2003-05-23 21:38 ` Kevin Ryde
2003-06-01 23:08 ` Marius Vollmer
2003-06-02 8:23 ` Martin Grabmueller
2003-06-02 15:58 ` Marius Vollmer [this message]
2003-06-03 6:56 ` Martin Grabmueller
2003-06-03 13:01 ` Marius Vollmer
2003-06-04 15:45 ` Kevin Ryde
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=87u1b8a2ts.fsf@zagadka.ping.de \
--to=mvo@zagadka.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).