From: Nala Ginrut <nalaginrut@gmail.com>
To: guile-devel@gnu.org
Subject: [PATCH] wrong description of string-rindex
Date: Tue, 10 Sep 2013 16:22:06 +0800 [thread overview]
Message-ID: <1378801326.4642.20.camel@Renee-desktop.suse> (raw)
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
- Scheme Procedure: string-rindex s char_pred [start [end]]
Search through the string S from right to left, returning the index
of the last occurrence of a character which
------
It's actually 'first occurrence', according to the activity of function.
And it's nonsense for 'last occurrence' since string-index does the same
work.
Here's a simple patch for that.
[-- Attachment #2: 0001-Fixed-typo-of-string-rindex-document.patch --]
[-- Type: text/x-patch, Size: 847 bytes --]
From 31fe00d36c834c8ca47f60af90ebf6b0b5a598a5 Mon Sep 17 00:00:00 2001
From: Nala Ginrut <nalaginrut@gmail.com>
Date: Tue, 10 Sep 2013 16:17:40 +0800
Subject: [PATCH] Fixed typo of string-rindex document
---
doc/ref/api-data.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ref/api-data.texi b/doc/ref/api-data.texi
index 7603180..f33a3cd 100644
--- a/doc/ref/api-data.texi
+++ b/doc/ref/api-data.texi
@@ -3715,7 +3715,7 @@ Return @code{#f} if no match is found.
@deffn {Scheme Procedure} string-rindex s char_pred [start [end]]
@deffnx {C Function} scm_string_rindex (s, char_pred, start, end)
Search through the string @var{s} from right to left, returning
-the index of the last occurrence of a character which
+the index of the first occurrence of a character which
@itemize @bullet
@item
--
1.7.10.4
next reply other threads:[~2013-09-10 8:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 8:22 Nala Ginrut [this message]
2013-09-10 10:49 ` [PATCH] wrong description of string-rindex Ian Price
2013-09-10 11:05 ` Nala Ginrut
-- strict thread matches above, loose matches on Subject: below --
2013-09-10 8:29 Nala Ginrut
2013-09-10 8:38 Nala Ginrut
2013-09-10 9:26 ` Taylan Ulrich B.
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=1378801326.4642.20.camel@Renee-desktop.suse \
--to=nalaginrut@gmail.com \
--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).