GNU bug report logs - #23111
25.0.92; logxor leading zero missed

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 23111 in the body.
You can then email your comments to 23111 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
To: bug-gnu-emacs <at> gnu.org
Subject: 25.0.92; logxor leading zero missed
Date: Fri, 25 Mar 2016 10:17:42 +0100

(logxor 110 011) ==> 101 ; right
(logxor 110 101) ==> 11  ; leading zero is missed

;;

In GNU Emacs 25.0.92.1 (i686-pc-linux-gnu, GTK+ Version 2.24.25)
 of 2016-03-03
Windowing system distributor 'The X.Org Foundation', version 11.0.11604000
System Description:    Debian GNU/Linux 8.3 (jessie)

Configured features:
XPM JPEG TIFF GIF PNG RSVG SOUND GPM DBUS GSETTINGS NOTIFY ACL LIBXML2
FREETYPE M17N_FLT LIBOTF XFT ZLIB TOOLKIT_SCROLL_BARS GTK2 X11

Important settings:
  value of $LANG: de_DE.utf8
  value of $XMODIFIERS: @im=ibus
  locale-coding-system: utf-8-unix

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  global-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

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

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message dired format-spec rfc822 mml
mml-sec epg epg-config gnus-util mm-decode mm-bodies mm-encode
mail-parse rfc2231 mailabbrev gmm-utils mailheader sendmail rfc2047
rfc2045 ietf-drums mm-util help-fns help-mode easymenu cl-loaddefs pcase
cl-lib mail-prsvr mail-utils time-date mule-util tooltip eldoc electric
uniquify ediff-hook vc-hooks lisp-float-type mwheel x-win
term/common-win x-dnd tool-bar dnd fontset image regexp-opt fringe
tabulated-list newcomment elisp-mode lisp-mode prog-mode register page
menu-bar rfn-eshadow timer select scroll-bar mouse jit-lock font-lock
syntax facemenu font-core 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 charscript case-table epa-hook jka-cmpr-hook help
simple abbrev 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
dbusbind inotify dynamic-setting system-font-setting font-render-setting
move-toolbar gtk x-toolkit x multi-tty make-network-process emacs)

Memory information:
((conses 8 159387 4604)
 (symbols 24 37793 0)
 (miscs 20 43 127)
 (strings 16 49999 5945)
 (string-bytes 1 716536)
 (vectors 8 12531)
 (vector-slots 4 449557 5660)
 (floats 8 167 310)
 (intervals 28 235 13)
 (buffers 520 11)
 (heap 1024 38620 797))

Message #8 received at 23111 <at> debbugs.gnu.org (full text, mbox):

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
Cc: 23111 <at> debbugs.gnu.org
Subject: Re: bug#23111: 25.0.92; logxor leading zero missed
Date: Fri, 25 Mar 2016 17:00:53 +0100

Andreas Röhler <andreas.roehler <at> easy-emacs.de> writes:

> (logxor 110 011) ==> 101 ; right
> (logxor 110 101) ==> 11  ; leading zero is missed

I think this is expected: logxor returns an integer, and "11" and "011"
are just different printed representations for the same number: 11.  The
lisp printer can't know that in this special case, it would make sense
to print 11 differently.  Even if it did, this wouldn't make any
difference for coding anyway.


Michael.

Message #17 received at 23111 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: 23111 <at> debbugs.gnu.org
Subject: Re: bug#23111: 25.0.92; logxor leading zero missed
Date: Fri, 25 Mar 2016 19:57:17 +0100

On 25.03.2016 17:00, Michael Heerdegen wrote:
> Andreas Röhler <andreas.roehler <at> easy-emacs.de> writes:
>
>> (logxor 110 011) ==> 101 ; right
>> (logxor 110 101) ==> 11  ; leading zero is missed
> I think this is expected: logxor returns an integer, and "11" and "011"
> are just different printed representations for the same number: 11.  The
> lisp printer can't know that in this special case, it would make sense
> to print 11 differently.  Even if it did, this wouldn't make any
> difference for coding anyway.
>
>
> Michael.

close 23111

Okay, thanks. Nesting it works as expected. Seem no problem indeed.

(logxor (logxor 110 101)(logxor 110 001)) ==> 100

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.