From: Philipp Stephani <p.stephani2@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
"Andreas Schwab" <schwab@linux-m68k.org>,
48678@debbugs.gnu.org
Subject: bug#48678: [PATCH] lex floats with trailing dot and exponent correctly
Date: Thu, 27 May 2021 14:37:42 +0200 [thread overview]
Message-ID: <CAArVCkRMZjgK806KF1SO9eXh-oEx2AR1bdBfsC8ts18owtFbjQ@mail.gmail.com> (raw)
In-Reply-To: <CAArVCkRjEnnzHYQ1QX0umRZTLme=CrDJhFvTXwhPtAacHhSq_Q@mail.gmail.com>
Am Do., 27. Mai 2021 um 14:36 Uhr schrieb Philipp Stephani
<p.stephani2@gmail.com>:
>
> Am Do., 27. Mai 2021 um 09:41 Uhr schrieb Lars Ingebrigtsen <larsi@gnus.org>:
> >
> > Andreas Schwab <schwab@linux-m68k.org> writes:
> >
> > > On Mai 27 2021, Lars Ingebrigtsen wrote:
> > >
> > >> Yes, it's a rather scary change -- people will have code that sloppily
> > >> parses noisy things like "1foo" and expect to get a 1 out, and ".e6"
> > >> could well be noise that they expect to have ignored.
> > >>
> > >> So I'm sceptical.
> > >
> > > But then 1.e6 should be parsed as a symbol.
> >
> > Oops, I thought this was about string-to-number, which it wasn't at all.
> >
> > Hm. Currently 1.e6 reads to 1? Weird.
>
> At least for me it's parsed as a symbol.
Oops, taking that back, I checked 1e.6 instead of 1.e6.
next prev parent reply other threads:[~2021-05-27 12:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 16:56 bug#48678: [PATCH] lex floats with trailing dot and exponent correctly Mattias Engdegård
2021-05-26 17:27 ` Eli Zaretskii
2021-05-26 22:13 ` Lars Ingebrigtsen
2021-05-27 7:32 ` Andreas Schwab
2021-05-27 7:40 ` Lars Ingebrigtsen
2021-05-27 12:28 ` Mattias Engdegård
2021-05-27 12:36 ` Philipp Stephani
2021-05-27 12:37 ` Philipp Stephani [this message]
2021-05-27 12:20 ` Mattias Engdegård
2021-05-29 6:03 ` Lars Ingebrigtsen
2021-05-29 7:47 ` Mattias Engdegård
2021-05-30 4:07 ` Lars Ingebrigtsen
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=CAArVCkRMZjgK806KF1SO9eXh-oEx2AR1bdBfsC8ts18owtFbjQ@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=48678@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.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).