From: Paul Eggert <eggert@cs.ucla.edu>
To: Helmut Eller <eller.helmut@gmail.com>, Andreas Schwab <schwab@suse.de>
Cc: 32252@debbugs.gnu.org
Subject: bug#32252: [PATCH] %o and %x now format signed numbers
Date: Thu, 26 Jul 2018 09:55:53 -0700 [thread overview]
Message-ID: <d79f1a10-bc5b-6982-4191-0adbadd4d40d@cs.ucla.edu> (raw)
In-Reply-To: <m2tvomfhhe.fsf@gmail.com>
On 07/26/2018 02:56 AM, Helmut Eller wrote:
> How often does one need to print a
> time value in hex notation?
It happens every time I run Emacs, in standard code shipped with Emacs.
I discovered this while doing compatibility checking before I proposed
this change. (The code in question continues to work just fine when
binary-as-unsigned is nil.)
> format-time-string doesn't even support that.
We're talking about 'format' not 'format-time-string', and Emacs code
does apply 'format' with %x to the tricky little integers that
'current-time' returns. It's a real hassle, and this hassle is pervasive
in Emacs. Having bignums would simplify it significantly.
And this problem is not limited to times. It's also file sizes, buffer
and string sizes (currently limited to fixnums, but they shouldn't be),
glyph codes, inode numbers, device numbers, file descriptor numbers,
inotify masks, windowing parameters, and other stuff I don't even know
about. It's pervasive and is a real hassle.
By the way, the format %x compatibility checking I mentioned is partly
why I have confidence that the practical effects of this change will be
minor. Many of the problems that I thought might happen, don't in fact
happen, because people who attempt to format negative numbers with %x
have already run into portability hassles on 32- vs 64-bit platforms,
and so they have written their code so that the platform choice doesn't
matter, either by ensuring that the integer is nonnegative or by not
caring what string is generated so long as it doesn't lose information.
Code written like this (and so far, that's all the code I've found)
works just fine when 'format' %x works like it does in Common Lisp or
Scheme.
next prev parent reply other threads:[~2018-07-26 16:55 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 19:12 bug#32252: [PATCH] %o and %x now format signed numbers Paul Eggert
2018-07-23 19:48 ` Helmut Eller
2018-07-23 19:49 ` Drew Adams
2018-07-23 23:30 ` Paul Eggert
2018-07-24 1:20 ` Drew Adams
2018-07-24 2:04 ` Paul Eggert
2018-07-24 2:38 ` Eli Zaretskii
2018-07-24 2:44 ` Paul Eggert
2018-07-24 14:29 ` Eli Zaretskii
2018-07-24 4:15 ` Drew Adams
2018-07-23 23:39 ` Paul Eggert
2018-07-24 1:16 ` Drew Adams
2018-07-25 3:53 ` Richard Stallman
2018-07-25 21:56 ` Drew Adams
2018-07-27 3:20 ` Richard Stallman
2018-07-24 4:49 ` Helmut Eller
2018-07-24 14:22 ` Paul Eggert
2018-07-24 14:35 ` Andreas Schwab
2018-07-24 18:15 ` Helmut Eller
2018-07-25 0:50 ` Paul Eggert
2018-07-25 2:41 ` Eli Zaretskii
2018-07-25 17:21 ` Paul Eggert
2018-07-25 17:28 ` Eli Zaretskii
2018-07-26 7:44 ` Paul Eggert
2018-07-26 8:04 ` Helmut Eller
2018-07-26 8:16 ` Paul Eggert
2018-07-25 6:58 ` Helmut Eller
2018-07-26 7:59 ` Paul Eggert
2018-07-26 8:43 ` Helmut Eller
2018-07-26 9:15 ` Paul Eggert
2018-07-26 9:39 ` Helmut Eller
2018-07-26 9:31 ` Andreas Schwab
2018-07-26 9:40 ` Robert Pluim
2018-07-26 9:56 ` Helmut Eller
2018-07-26 16:55 ` Paul Eggert [this message]
2018-07-26 17:16 ` Helmut Eller
2018-07-26 17:50 ` Paul Eggert
2018-07-26 18:35 ` Helmut Eller
2018-07-26 21:07 ` Paul Eggert
2018-07-24 18:27 ` Eli Zaretskii
2018-07-25 0:54 ` Paul Eggert
2018-07-25 8:09 ` Andreas Schwab
2018-07-25 20:16 ` Paul Eggert
2018-07-25 14:17 ` Eli Zaretskii
2018-07-25 23:33 ` Brett Gilio
2018-07-26 7:26 ` Paul Eggert
2018-07-24 16:26 ` Andy Moreton
2018-07-25 10:08 ` Andy Moreton
2018-07-26 12:52 ` Andy Moreton
2018-07-26 12:54 ` Andy Moreton
2018-07-26 17:18 ` Helmut Eller
2018-08-23 9:37 ` Helmut Eller
2022-07-04 1:03 ` bug#32252: i find binary-as-unsigned to be very helpful snickerbockers
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d79f1a10-bc5b-6982-4191-0adbadd4d40d@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=32252@debbugs.gnu.org \
--cc=eller.helmut@gmail.com \
--cc=schwab@suse.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).