From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: "Vincent Belaïche" <vincent.b.1@hotmail.fr>, 43764@debbugs.gnu.org
Subject: bug#43764: Calc shift right broken
Date: Tue, 06 Oct 2020 03:28:56 +0200 [thread overview]
Message-ID: <87wo04nnvr.fsf@gnus.org> (raw)
In-Reply-To: <F8DEC5ED-BA00-414E-9E5D-848AD7533783@acm.org> ("Mattias Engdegård"'s message of "Mon, 5 Oct 2020 12:34:15 +0200")
Mattias Engdegård <mattiase@acm.org> writes:
>> But if we're changing the number of default bits, perhaps it would make
>> more sense to default to having no bit width restrictions? Or would
>> that entail major Calc surgery?
>
> Any changes to Calc, however minor, are fraught with danger and excitement!
:-)
> Fun as it may be, better not making changes speculatively though.
> (On the other hand it could be that everyone have been bothered about
> this for years. I have no way of knowing.)
In olden times, I would guess most people thought that it just had to be
this way. But now that the rest of Emacs has bignums, it's perhaps more
surprising that Calc behaves this way when doing shifts.
On the other hand, I don't know what people use Calc for here. If
people are going "I wonder what would happen on a 32-bit machine if I
were to do this shift operation", then it'd be something else...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-06 1:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 15:28 bug#43764: Calc shift right broken Vincent Belaïche
2020-10-02 20:49 ` Mattias Engdegård
2020-10-05 8:12 ` Lars Ingebrigtsen
2020-10-05 10:34 ` Mattias Engdegård
2020-10-06 1:28 ` Lars Ingebrigtsen [this message]
2020-10-08 12:24 ` Mattias Engdegård
2020-10-09 15:29 ` Mattias Engdegård
2020-10-09 15:34 ` Vincent Belaïche
2020-10-10 16:24 ` Mattias Engdegård
2020-10-10 16:31 ` Mattias Engdegård
2020-10-13 9:56 ` Mattias Engdegård
2020-11-04 11:14 ` Vincent Belaïche
2020-11-04 11:54 ` Mattias Engdegård
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=87wo04nnvr.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=43764@debbugs.gnu.org \
--cc=mattiase@acm.org \
--cc=vincent.b.1@hotmail.fr \
/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).