From: Keith Seitz <keiths@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH Bug breakpoints/14381] Fix linespec to parse file name that begin with decimal numbers
Date: Sun, 22 Jul 2012 14:12:00 -0000 [thread overview]
Message-ID: <500C0A1F.8040106@redhat.com> (raw)
In-Reply-To: <CANFwon22Tt57WcsDE8rPrSjgxg62MbgsN0WrAELu9Y52RDwUGg@mail.gmail.com>
On 07/21/2012 11:30 PM, Hui Zhu wrote:
> @@ -390,6 +392,12 @@ linespec_lexer_lex_number (linespec_pars
> ++(PARSER_STREAM (parser));
> }
>
> + if (*PARSER_STREAM (parser) != '\0' && !isspace(*PARSER_STREAM (parser)))
> + {
> + PARSER_STREAM (parser) = LS_TOKEN_STOKEN (token).ptr;
> + return linespec_lexer_lex_string (parser);
> + }
> +
> return token;
> }
>
This obfuscates the meaning of linespec_lexer_lex_number. A better place
to deal with this is in linespec_lexer_lex_one directly where the
decision to call linespec_lexer_lex_number is made.
That can either be done by inspecting the input stream directly in
*_lex_one or by having *_lex_number error (add a new error token type)
and then having linespec_lexer_lex_one fallback to string lexing.
Keith
next prev parent reply other threads:[~2012-07-22 14:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 6:30 Hui Zhu
2012-07-22 7:11 ` Jan Kratochvil
2012-07-22 8:55 ` Hui Zhu
2012-07-22 10:11 ` Hui Zhu
2012-07-22 10:52 ` Jan Kratochvil
2012-07-23 14:26 ` Tom Tromey
2012-07-23 18:04 ` Keith Seitz
2012-07-22 14:12 ` Keith Seitz [this message]
2012-07-22 14:48 ` Hui Zhu
2012-07-23 14:28 ` Tom Tromey
2012-07-23 17:17 ` Keith Seitz
2012-07-24 3:48 ` Hui Zhu
2012-07-24 19:36 ` Tom Tromey
2012-07-25 12:57 ` Hui Zhu
2012-07-25 21:21 ` Keith Seitz
2012-07-26 13:52 ` Tom Tromey
2012-07-26 18:21 ` Keith Seitz
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=500C0A1F.8040106@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=teawater@gmail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox