From: Vitalie Spinu <spinuvit@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 14254@debbugs.gnu.org
Subject: bug#14254: 24.3; read-number fails to recognize faulty numbers (string-to-number to blame)
Date: Wed, 24 Apr 2013 16:48:04 +0200 [thread overview]
Message-ID: <877gjsast7.fsf@gmail.com> (raw)
In-Reply-To: <m2vc7cypp3.fsf@igel.home> (Andreas Schwab's message of "Wed, 24 Apr 2013 16:21:28 +0200")
>> Andreas Schwab <schwab@linux-m68k.org>
>> on Wed, 24 Apr 2013 16:21:28 +0200 wrote:
> Vitalie Spinu <spinuvit@gmail.com> writes:
>> Now (string-to-number "junk") returns 0.
> It always did, as documented.
That presumably means that read-number never worked as originally
expected. The comment in source file says that read-number should be
used for "n" interactive spec, but "n" spec works as expected, so
read-number is not used there.
Wouldn't it be more natural for string-to-number to return nil rather
than 0 in a non-number case?
Vitalie
next prev parent reply other threads:[~2013-04-24 14:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 12:46 bug#14254: 24.3; read-number fails to recognize faulty numbers (string-to-number to blame) Vitalie Spinu
2013-04-24 13:09 ` bug#14254: 24.3; read-number fails to recognize faulty numbers (string-to-number toblame) Drew Adams
2013-04-24 14:21 ` bug#14254: 24.3; read-number fails to recognize faulty numbers (string-to-number to blame) Andreas Schwab
2013-04-24 14:44 ` bug#14254: 24.3; read-number fails to recognize faulty numbers (string-to-number toblame) Drew Adams
2013-04-24 14:48 ` Vitalie Spinu [this message]
2013-04-24 15:13 ` Drew Adams
2013-04-24 17:29 ` bug#14254: 24.3; read-number fails to recognize faulty numbers (string-to-number to blame) Glenn Morris
2013-04-24 20:57 ` Juri Linkov
2013-04-25 3:33 ` Stefan Monnier
2013-04-25 20:44 ` Juri Linkov
2013-04-26 1:46 ` Stefan Monnier
2013-05-07 8:42 ` Juri Linkov
2013-05-07 13:38 ` Stefan Monnier
2013-05-07 20:51 ` Juri Linkov
2013-05-07 21:31 ` 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=877gjsast7.fsf@gmail.com \
--to=spinuvit@gmail.com \
--cc=14254@debbugs.gnu.org \
--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).