From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: evaluating numbers Date: Fri, 15 Nov 2019 10:14:23 +0200 Message-ID: <837e414kv4.fsf@gnu.org> References: <875zjw2emg.fsf@gmx.net> <618B38D9-CD34-4200-8CA1-1A6B0922A83A@traduction-libre.org> <871ruk2d3f.fsf@gmx.net> <3C929D7B-1C10-4713-9EDA-55C80FC36AD8@traduction-libre.org> <835zjvg385.fsf@gnu.org> <83sgmyd6rw.fsf@gnu.org> <835zjucwbz.fsf@gnu.org> <628A3663-BDD3-47C5-B4F4-E260FD900691@traduction-libre.org> <83o8xla50f.fsf@gnu.org> <8336ex9sow.fsf@gnu.org> <4836980E-C425-466C-BB86-5E962C4B3F96@traduction-libre.org> <87zhh440lw.fsf@hase.home> <87y2wn7ot1.fsf@mail.linkov.net> <87a791nntq.fsf@mail.linkov.net> <831rua7hjg.fsf@gnu.org> <87imnmdqcw.fsf@mail.linkov.net> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="116051"; mail-complaints-to="usenet@blaine.gmane.org" Cc: jean.christophe.helary@traduction-libre.org, schwab@linux-m68k.org, emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 15 09:15:34 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iVWlP-000U2R-Tk for ged-emacs-devel@m.gmane.org; Fri, 15 Nov 2019 09:15:32 +0100 Original-Received: from localhost ([::1]:36554 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iVWlO-0007CI-Ot for ged-emacs-devel@m.gmane.org; Fri, 15 Nov 2019 03:15:30 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41727) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iVWkY-0007B6-ON for emacs-devel@gnu.org; Fri, 15 Nov 2019 03:14:39 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:40860) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iVWkY-0007Vj-8M; Fri, 15 Nov 2019 03:14:38 -0500 Original-Received: from [176.228.60.248] (port=3822 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1iVWkX-00057y-JE; Fri, 15 Nov 2019 03:14:38 -0500 In-reply-to: <87imnmdqcw.fsf@mail.linkov.net> (message from Juri Linkov on Fri, 15 Nov 2019 00:50:55 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:242217 Archived-At: > From: Juri Linkov > 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.