bug#30218: 27.0.50; Possibly incorrect statement in manual about string equality

bug#30218: 27.0.50; Possibly incorrect statement in manual about string equality

[Philipp]

The manual says in the section "Equality Predicates":

     For technical reasons, a unibyte string
     and a multibyte string are ‘equal’ if and only if they contain the
     same sequence of character codes and all these codes are either in
     the range 0 through 127 (ASCII) or 160 through 255
     (‘eight-bit-graphic’).

However, that doesn't seem to be the case:

(equal (string #xA0) (unibyte-string #xA0)) => nil
(equal (string #x3FFFA0) (unibyte-string #xA0)) => nil


In GNU Emacs 27.0.50 (build 10, x86_64-apple-darwin17.3.0, NS appkit-1561.20 Version 10.13.2 (Build 17C205))
 of 2018-01-22 built on p
Repository revision: 3558d96b60393893a346f4382b813ca0738f9d9b
Windowing system distributor 'Apple', version 10.3.1561
System Description:  Mac OS X 10.13.2

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.

Configured using:
 'configure --without-threads --with-modules --without-pop
 --with-mailutils --enable-gcc-warnings=yes --enable-checking
 --enable-check-lisp-object-type 'CFLAGS=-ggdb3 -O0''

Configured features:
NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES JSON

Important settings:
  value of $LANG: de_DE.UTF-8
  locale-coding-system: utf-8-unix

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  global-eldoc-mode: t
  eldoc-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message rmc puny seq byte-opt gv
bytecomp byte-compile cconv cl-loaddefs cl-lib dired dired-loaddefs
format-spec rfc822 mml easymenu mml-sec password-cache epa derived epg
epg-config gnus-util rmail rmail-loaddefs mm-decode mm-bodies mm-encode
mail-parse rfc2231 mailabbrev gmm-utils mailheader sendmail rfc2047
rfc2045 ietf-drums mm-util mail-prsvr mail-utils elec-pair time-date
tooltip eldoc electric uniquify ediff-hook vc-hooks lisp-float-type
mwheel term/ns-win ns-win ucs-normalize mule-util term/common-win
tool-bar dnd fontset image regexp-opt fringe tabulated-list replace
newcomment text-mode elisp-mode lisp-mode prog-mode register page
menu-bar rfn-eshadow isearch timer select scroll-bar mouse jit-lock
font-lock syntax facemenu font-core term/tty-colors frame cl-generic
cham georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao
korean japanese eucjp-ms cp51932 hebrew greek romanian slovak czech
european ethiopic indian cyrillic chinese composite charscript charprop
case-table epa-hook jka-cmpr-hook help simple abbrev obarray minibuffer
cl-preloaded nadvice loaddefs button faces cus-face macroexp files
text-properties overlay sha1 md5 base64 format env code-pages mule
custom widget hashtable-print-readable backquote kqueue cocoa ns
multi-tty make-network-process emacs)

Memory information:
((conses 16 204836 8305)
 (symbols 48 20154 1)
 (miscs 40 57 148)
 (strings 32 28905 2033)
 (string-bytes 1 771731)
 (vectors 16 35241)
 (vector-slots 8 721872 13820)
 (floats 8 52 64)
 (intervals 56 208 0)
 (buffers 992 11))

bug#30218: [PATCH] Fix statement about string equality (Bug#30218).

[Philipp Stephani]

* doc/lispref/objects.texi (Equality Predicates): Fix statement about
equality between unibyte and multibyte strings.
---
 doc/lispref/objects.texi | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/doc/lispref/objects.texi b/doc/lispref/objects.texi
index 7cbc61dc8e..82c8007376 100644
--- a/doc/lispref/objects.texi
+++ b/doc/lispref/objects.texi
@@ -2206,11 +2206,10 @@ Equality Predicates
 Comparison of strings is case-sensitive, but does not take account of
 text properties---it compares only the characters in the strings.
 @xref{Text Properties}.  Use @code{equal-including-properties} to also
-compare text properties.  For technical reasons, a unibyte string and
-a multibyte string are @code{equal} if and only if they contain the
-same sequence of character codes and all these codes are either in the
-range 0 through 127 (@acronym{ASCII}) or 160 through 255
-(@code{eight-bit-graphic}).  (@pxref{Text Representations}).
+compare text properties.  A unibyte string and a multibyte string are
+@code{equal} if and only if they contain the same sequence of
+character codes and all these codes are in the range 0 through 127
+(@acronym{ASCII}).  (@pxref{Text Representations}).
 
 @example
 @group
-- 
2.15.1

bug#30218: 27.0.50; Possibly incorrect statement in manual about string equality

[Eli Zaretskii]

> From: Philipp <p.stephani2@gmail.com>
> Date: Mon, 22 Jan 2018 23:50:16 +0100
> 
> 
> The manual says in the section "Equality Predicates":
> 
>      For technical reasons, a unibyte string
>      and a multibyte string are ‘equal’ if and only if they contain the
>      same sequence of character codes and all these codes are either in
>      the range 0 through 127 (ASCII) or 160 through 255
>      (‘eight-bit-graphic’).
> 
> However, that doesn't seem to be the case:
> 
> (equal (string #xA0) (unibyte-string #xA0)) => nil
> (equal (string #x3FFFA0) (unibyte-string #xA0)) => nil

Thanks, fixed.

bug#30218: [PATCH] Fix statement about string equality (Bug#30218).

[Philipp Stephani]

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

Philipp Stephani <p.stephani2@gmail.com> schrieb am Di., 23. Jan. 2018 um
00:13 Uhr:

> * doc/lispref/objects.texi (Equality Predicates): Fix statement about
> equality between unibyte and multibyte strings.
>

Eli has already pushed an equivalent fix in the meantime, so this patch is
no longer relevant.

[-- Attachment #2: Type: text/html, Size: 586 bytes --]