From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: jean.christophe.helary@traduction-libre.org,
schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: Re: evaluating numbers
Date: Fri, 15 Nov 2019 10:14:23 +0200 [thread overview]
Message-ID: <837e414kv4.fsf@gnu.org> (raw)
In-Reply-To: <87imnmdqcw.fsf@mail.linkov.net> (message from Juri Linkov on Fri, 15 Nov 2019 00:50:55 +0200)
> From: Juri Linkov <juri@linkov.net>
> Cc: schwab@linux-m68k.org, jean.christophe.helary@traduction-libre.org,
> emacs-devel@gnu.org
> Date: Fri, 15 Nov 2019 00:50:55 +0200
>
> Ok, will use this text. But I have more doubts about using (max-char).
> What if this .el is compiled on 64-bit, where a larger value of 'max-char'
> will be saved to .elc, but loaded on 32-bit. Will it fail to load such .elc?
max-char yields a 22-bit value, so it fits an integer in any Emacs
build.
> Maybe instead of (max-char) it would be better to use the value 't'
> to mean no limitation. Then to check this value explicitly
> in the implementation of 'eval-expression-print-format'.
IMO, that'd be over-engineering, since the max Unicode codepoint is
unlikely to change any time soon.
next prev parent reply other threads:[~2019-11-15 8:14 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 9:43 evaluating numbers Jean-Christophe Helary
2019-11-07 9:57 ` Stephen Berman
2019-11-07 10:20 ` Jean-Christophe Helary
2019-11-07 10:30 ` Stephen Berman
2019-11-07 10:40 ` Jean-Christophe Helary
2019-11-07 14:39 ` Eli Zaretskii
2019-11-08 0:36 ` Jean-Christophe Helary
2019-11-08 10:03 ` Eli Zaretskii
2019-11-08 12:23 ` Jean-Christophe Helary
2019-11-08 13:22 ` Stefan Monnier
2019-11-09 0:20 ` Jean-Christophe Helary
2019-11-09 7:24 ` Eli Zaretskii
2019-11-08 13:49 ` Eli Zaretskii
2019-11-09 0:15 ` Jean-Christophe Helary
2019-11-09 7:22 ` Eli Zaretskii
2019-11-09 11:18 ` Jean-Christophe Helary
2019-11-09 11:48 ` Eli Zaretskii
2019-11-10 0:59 ` Jean-Christophe Helary
2019-11-10 8:06 ` Andreas Schwab
2019-11-10 20:52 ` Juri Linkov
2019-11-12 20:28 ` Juri Linkov
2019-11-12 22:05 ` Drew Adams
2019-11-12 22:21 ` Eli Zaretskii
2019-11-12 23:30 ` Drew Adams
2019-11-13 8:10 ` Eli Zaretskii
2019-11-13 14:47 ` Drew Adams
2019-11-14 12:45 ` Eli Zaretskii
2019-11-14 22:50 ` Juri Linkov
2019-11-14 23:40 ` Noam Postavsky
2019-11-15 8:14 ` Eli Zaretskii [this message]
2019-11-14 9:22 ` Eli Zaretskii
2019-11-14 9:46 ` Yuri Khan
2019-11-14 11:36 ` Jean-Christophe Helary
2019-11-14 13:55 ` Stefan Monnier
2019-11-14 13:59 ` Noam Postavsky
2019-11-14 14:17 ` Stefan Monnier
2019-11-14 21:44 ` Juanma Barranquero
2019-11-14 14:03 ` Andreas Schwab
2019-11-14 14:10 ` Eli Zaretskii
2019-11-14 17:10 ` Paul Eggert
2019-11-14 18:32 ` Eli Zaretskii
2019-11-14 18:39 ` Eli Zaretskii
2019-11-15 8:32 ` Štěpán Němec
2019-11-15 14:54 ` Robert Pluim
2019-11-15 15:16 ` Eli Zaretskii
2019-11-15 15:32 ` Eli Zaretskii
2019-11-15 15:55 ` Robert Pluim
2019-11-15 16:00 ` Robert Pluim
2019-11-15 16:11 ` Lars Ingebrigtsen
2019-11-15 16:33 ` Robert Pluim
2019-11-15 16:13 ` Eli Zaretskii
2019-11-17 2:15 ` Richard Stallman
2019-11-17 20:02 ` Robert Pluim
2019-11-18 16:25 ` Eli Zaretskii
2019-11-18 16:54 ` Robert Pluim
2019-11-18 17:05 ` Eli Zaretskii
2019-11-20 13:00 ` Robert Pluim
2019-11-20 16:40 ` Eli Zaretskii
2019-11-20 17:09 ` Robert Pluim
2019-11-20 17:45 ` Eli Zaretskii
2019-11-19 6:08 ` Richard Stallman
2019-11-19 9:50 ` Robert Pluim
2019-11-15 15:53 ` Robert Pluim
2019-11-15 16:13 ` Eli Zaretskii
2019-11-15 16:43 ` Robert Pluim
2019-11-15 16:59 ` Eli Zaretskii
2019-11-16 20:40 ` Juri Linkov
2019-11-17 17:34 ` Eli Zaretskii
2019-11-17 21:16 ` Juri Linkov
2019-11-14 22:56 ` Juri Linkov
2019-11-09 16:03 ` Stefan Monnier
2019-11-10 0:22 ` Jean-Christophe Helary
2019-11-10 4:47 ` Stefan Monnier
2019-11-13 23:02 ` Jean-Christophe Helary
2019-11-14 13:52 ` Stefan Monnier
2019-11-14 9:20 ` Eli Zaretskii
2019-11-14 11:35 ` Jean-Christophe Helary
2019-11-14 13:37 ` Noam Postavsky
2019-11-14 14:20 ` Eli Zaretskii
2019-11-15 10:36 ` Jean-Christophe Helary
2019-11-15 13:03 ` Eli Zaretskii
2020-04-28 14:52 ` Jean-Christophe Helary
2020-04-28 15:05 ` Eli Zaretskii
2020-04-28 17:28 ` Paul Eggert
2020-04-28 23:16 ` Jean-Christophe Helary
2020-04-29 0:08 ` Paul Eggert
2020-04-29 0:21 ` Jean-Christophe Helary
2020-04-29 7:08 ` Eli Zaretskii
2020-04-29 8:00 ` Jean-Christophe Helary
2020-04-29 3:23 ` Richard Stallman
2020-04-29 3:49 ` Jean-Christophe Helary
2020-04-29 3:51 ` Stefan Monnier
2020-04-29 10:09 ` Po Lu
2020-04-30 2:34 ` Richard Stallman
2020-04-30 3:04 ` Stefan Monnier
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=837e414kv4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@traduction-libre.org \
--cc=juri@linkov.net \
--cc=schwab@linux-m68k.org \
/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).