From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [FYI] Make the Rust parser pure
Date: Fri, 20 Jul 2018 15:28:00 -0000 [thread overview]
Message-ID: <87tvou3p2b.fsf@tromey.com> (raw)
In-Reply-To: <20180720152524.7062-1-tom@tromey.com> (Tom Tromey's message of "Fri, 20 Jul 2018 09:25:24 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> This makes the Rust parser a pure parser and removes all the
Tom> (non-constant) globals from rust-exp.y. This seemed like a nice
Tom> simplification to me and I think it should probably be applied to all
Tom> the parsers. Perhaps it would be good to go even one step farther and
Tom> have all parsers derive from parser_state.
Tom> Tested on x86-64 Fedora 26.
Actually, I will have to update this, because I tried it again with
byacc and now it fails.
Tom
next prev parent reply other threads:[~2018-07-20 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 15:25 Tom Tromey
2018-07-20 15:28 ` Tom Tromey [this message]
2018-07-20 15:39 ` Tom Tromey
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=87tvou3p2b.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox