GNU bug report logs -
#13081
24.3.50; doc of `compare-strings' says nothing about the compare function used
Previous Next
Reported by: "Drew Adams" <drew.adams <at> oracle.com>
Date: Tue, 4 Dec 2012 18:36:02 UTC
Severity: minor
Found in version 24.3.50
Done: Chong Yidong <cyd <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 13081 in the body.
You can then email your comments to 13081 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13081
; Package
emacs
.
(Tue, 04 Dec 2012 18:36:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
"Drew Adams" <drew.adams <at> oracle.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Tue, 04 Dec 2012 18:36:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
The doc mentions case-sensitivity, and it says what the function does if
the specified portions match etc. But it says NOTHING (apart from
possibly ignoring case) about what "matching" means. Is lexicographic
order used?
How can you document a function about comparing two sequences without
defining/mentioning the helper function that is used to compare two
elements, one from each sequence?
In GNU Emacs 24.3.50.1 (i386-mingw-nt5.1.2600)
of 2012-12-03 on MS-W7-DANI
Bzr revision: 111077
agustin.martin <at> hispalinux.es-20121203172342-ifsebjmhksk28qa9
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
`configure --with-gcc (4.7) --no-opt --enable-checking --cflags
-Ic:/emacs/libs/libXpm-3.5.10/include -Ic:/emacs/libs/libXpm-3.5.10/src
-Ic:/emacs/libs/libpng-1.2.37-lib/include -Ic:/emacs/libs/zlib-1.2.5
-Ic:/emacs/libs/giflib-4.1.4-1-lib/include
-Ic:/emacs/libs/jpeg-6b-4-lib/include
-Ic:/emacs/libs/tiff-3.8.2-1-lib/include
-Ic:/emacs/libs/libxml2-2.7.8-w32-bin/include/libxml2
-Ic:/emacs/libs/gnutls-3.0.9-w32-bin/include
-Ic:/emacs/libs/libiconv-1.9.2-1-lib/include'
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13081
; Package
emacs
.
(Tue, 04 Dec 2012 18:45:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 13081 <at> debbugs.gnu.org (full text, mbox):
1. I should have said that the doc problem applies to both the doc string and
Elisp manual.
2. What's more, the doc string says that "END1 and END2 default to". This
language is incorrect - there is no defaulting. These parameters are mandatory,
so they do not have any default values.
What the doc should say is two things:
a. START1, START2, END1, and END2 are either 0-based indexes into the string.
(This information is missing.)
b. START1, START2, END1, and END2 can each alternatively be nil. For START1 and
START2, nil is the same as 0. For END1 and END2, nil is the same as the length
of STR1 and STR2, respectively.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13081
; Package
emacs
.
(Tue, 04 Dec 2012 18:51:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 13081 <at> debbugs.gnu.org (full text, mbox):
> a. START1, START2, END1, and END2 are either 0-based indexes
> into the string. (This information is missing.)
>
> b. START1, START2, END1, and END2 can each alternatively be
> nil.
Typo in above text: strike the "either". Or else add "or nil" after "either"
and rephrase (b) to just say what happens when nil.
Reply sent
to
Chong Yidong <cyd <at> gnu.org>
:
You have taken responsibility.
(Sat, 15 Dec 2012 13:46:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
"Drew Adams" <drew.adams <at> oracle.com>
:
bug acknowledged by developer.
(Sat, 15 Dec 2012 13:46:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 13081-done <at> debbugs.gnu.org (full text, mbox):
"Drew Adams" <drew.adams <at> oracle.com> writes:
> The doc mentions case-sensitivity, and it says what the function does if
> the specified portions match etc. But it says NOTHING (apart from
> possibly ignoring case) about what "matching" means. Is lexicographic
> order used?
Fixed, thanks. (The other issues too.)
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 13 Jan 2013 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 11 years and 129 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.