From: Noah Lavine <noah.b.lavine@gmail.com>
To: bug-guile@gnu.org
Subject: [Patch] Documentation Fix
Date: Mon, 3 Jan 2011 18:02:27 -0500 [thread overview]
Message-ID: <AANLkTi=HjD_ALfQt5otqYbyVUG1o8psds76heyoe384f@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 202 bytes --]
Hello all,
I was looking in the documentation at the string-index and
string-rindex functions, and I realized that it didn't say what they
did if they didn't find a match. This patch fixes that.
Noah
[-- Attachment #2: 0001-Document-string-index.patch --]
[-- Type: application/octet-stream, Size: 1163 bytes --]
From 19bb0db0194de31a787627c67ba73d6258ea710e Mon Sep 17 00:00:00 2001
From: Noah Lavine <nlavine@haverford.edu>
Date: Mon, 3 Jan 2011 17:58:36 -0500
Subject: [PATCH] Document string-index
Add a note to the documentation that if the string-index and string-rindex
procedures do not find a match for their predicate, they will return #f.
---
doc/ref/api-data.texi | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/doc/ref/api-data.texi b/doc/ref/api-data.texi
index 14b81f5..13b566f 100755
--- a/doc/ref/api-data.texi
+++ b/doc/ref/api-data.texi
@@ -3398,6 +3398,8 @@ satisfies the predicate @var{char_pred}, if it is a procedure,
@item
is in the set @var{char_pred}, if it is a character set.
@end itemize
+
+Returns #f if no match is found.
@end deffn
@deffn {Scheme Procedure} string-rindex s char_pred [start [end]]
@@ -3415,6 +3417,8 @@ satisfies the predicate @var{char_pred}, if it is a procedure,
@item
is in the set if @var{char_pred} is a character set.
@end itemize
+
+Returns #f if no match is found.
@end deffn
@deffn {Scheme Procedure} string-prefix-length s1 s2 [start1 [end1 [start2 [end2]]]]
--
1.7.3.2
next reply other threads:[~2011-01-03 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 23:02 Noah Lavine [this message]
2011-01-04 17:09 ` [Patch] Documentation Fix Ludovic Courtès
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='AANLkTi=HjD_ALfQt5otqYbyVUG1o8psds76heyoe384f@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--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).