From: Paul Eggert <eggert@cs.ucla.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: documentation of integers, fixnums and bignums
Date: Sat, 8 Sep 2018 13:15:54 -0700 [thread overview]
Message-ID: <92915cae-21d5-c365-89f2-3a15fc9114c4@cs.ucla.edu> (raw)
In-Reply-To: <jwvmusronz1.fsf-monnier+gmane.emacs.devel@gnu.org>
Stefan Monnier wrote:
>> encode-char could potentially return a value that cannot be
>> represented as a fixnum.
> Can this still happen? When?
When INDEX_TO_CODE_POINT returns a code point greater than most-positive-fixnum,
which can happen (in theory, at least) on 32-bit platforms. Formerly, such a
code point caused Emacs to return a negative fixnum or junk, depending on the
code point. Now it causes Emacs to return an integer with the proper value.
I don't know of any charsets that actually do that. Possibly Emacs should simply
report an error if it runs across one, as that would simplify the code point
processing internals.
next prev parent reply other threads:[~2018-09-08 20:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-08 16:09 documentation of integers, fixnums and bignums Paul Eggert
2018-09-08 16:27 ` Eli Zaretskii
2018-09-08 18:15 ` Stefan Monnier
2018-09-08 20:15 ` Paul Eggert [this message]
2018-09-08 22:03 ` Stefan Monnier
2018-09-08 23:37 ` Paul Eggert
2018-09-09 2:33 ` Stefan Monnier
2018-09-09 5:40 ` Eli Zaretskii
2018-09-10 0:09 ` Stefan Monnier
2018-09-10 6:43 ` Eli Zaretskii
2018-09-10 12:11 ` Stefan Monnier
2018-09-10 13:53 ` Eli Zaretskii
2018-09-09 5:42 ` Eli Zaretskii
2018-09-10 0:12 ` Stefan Monnier
2018-09-08 20:05 ` Paul Eggert
2018-09-08 21:07 ` Eli Zaretskii
2018-09-08 21:58 ` Stefan Monnier
[not found] <<0f632217-27ad-4f54-8ce0-480301fa2a86@cs.ucla.edu>
[not found] ` <<83pnxorm37.fsf@gnu.org>
2018-09-09 1:43 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92915cae-21d5-c365-89f2-3a15fc9114c4@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.