unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: Re: doco srfi-13 string-replace
Date: Thu, 05 Jun 2003 01:45:36 +1000	[thread overview]
Message-ID: <87el29kfrz.fsf@zip.com.au> (raw)
In-Reply-To: 87u1b8a2ts.fsf@zagadka.ping.de

[-- Attachment #1: Type: text/plain, Size: 267 bytes --]

Marius Vollmer <mvo@zagadka.de> writes:
>
> So, please
> document that behavior but clearly mark it as a "Guile extension".

I made this addition,

	* srfi-modules.texi (SRFI-13 Miscellaneous): In string-replace, note
	start1 and end1 optional is a Guile extension.


[-- Attachment #2: srfi-modules.texi.string-replace-optional.diff --]
[-- Type: text/plain, Size: 509 bytes --]

--- srfi-modules.texi.~1.16.~	2003-05-24 09:42:30.000000000 +1000
+++ srfi-modules.texi	2003-06-05 01:45:02.000000000 +1000
@@ -1803,6 +1803,9 @@
 Return the string @var{s1}, but with the characters
 @var{start1} @dots{} @var{end1} replaced by the characters
 @var{start2} @dots{} @var{end2} from @var{s2}.
+
+For reference, note that SRFI-13 specifies @var{start1} and @var{end1}
+as mandatory, but in Guile they are optional.
 @end deffn
 
 @deffn {Scheme Procedure} string-tokenize s [token-set start end]

[-- Attachment #3: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

      parent reply	other threads:[~2003-06-04 15:45 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
2003-06-03  6:56         ` Martin Grabmueller
2003-06-03 13:01           ` Marius Vollmer
2003-06-04 15:45         ` Kevin Ryde [this message]

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=87el29kfrz.fsf@zip.com.au \
    --to=user42@zip.com.au \
    /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).