[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#32252: [PATCH] %o and %x now format signed numbers

From: Paul Eggert
Subject: bug#32252: [PATCH] %o and %x now format signed numbers
Date: Thu, 26 Jul 2018 02:15:52 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1

Helmut Eller wrote:
And prohibit %x on bignums? That would make little sense.
It would prohibit only negative bignums just like negative flonums are

So under this proposal %x would generate ambiguous output once we add bignums? For example, on a 32-bit platform (format "%x" -1) would generate the same output as (format "%x" #x3fffffff), even though -1 and #x3fffffff would be different integers? That doesn't sound like a good idea.

it would make much more sense to print flonums the way %a does in C

It would make sense to add an %a specification, like C's %a. But C's %a formats floating-point numbers, and surely Emacs Lisp's %a should be similar. That is, %a should treat integers the way the other floating-point specs do (%e, %f, %g).

Common Lisp and Scheme don't have any such prohibition; why should
Emacs Lisp?

Because Emacs Lisp was very successful without bignums.

This appears to be more an argument against bignums than anything else. I've used Emacs Lisp without bignums for many years, and it's *always* been a hindrance. I would much rather have bignums, as they would make a lot of things simpler. I agree that Emacs Lisp does not much need complex numbers or ratios.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]