From: Daniel Jacobowitz <drow@false.org>
To: Rob Quill <rob.quill@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: YACC/Lex
Date: Mon, 09 Oct 2006 12:33:00 -0000 [thread overview]
Message-ID: <20061009123343.GA11055@nevyn.them.org> (raw)
In-Reply-To: <baf6008d0610090444lec06d1eg71fa24705d5ab423@mail.gmail.com>
On Mon, Oct 09, 2006 at 12:44:56PM +0100, Rob Quill wrote:
> Hi,
>
> Is it ok to use code generated by YACC and/or Lex in GDB? If not, what
> alternatives are there?
Take a look at the several existing yacc parsers in GDB; there's also
at least one lex parser.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-09 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 11:45 YACC/Lex Rob Quill
2006-10-09 12:33 ` Daniel Jacobowitz [this message]
2006-10-09 18:14 ` YACC/Lex Michael Snyder
2006-10-09 20:09 ` YACC/Lex Rob Quill
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=20061009123343.GA11055@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=rob.quill@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