From: Jim Blandy <jimb@codesourcery.com>
To: "Pierre Muller" <muller@ics.u-strasbg.fr>
Cc: <gdb@sourceware.org>
Subject: Re: Question about ARI for expression parsers
Date: Sat, 28 Jul 2007 00:02:00 -0000 [thread overview]
Message-ID: <m3odhxd98q.fsf@codesourcery.com> (raw)
In-Reply-To: <002d01c7d02f$11e9e510$35bdaf30$@u-strasbg.fr> (Pierre Muller's message of "Fri, 27 Jul 2007 11:18:18 +0200")
"Pierre Muller" <muller@ics.u-strasbg.fr> writes:
> I just sent an email to gdb-patches about
> fixes for p-valprint.c regarding ARI reports.
>
> I noticed that, in the pascal specific files
> that I maintain, there are lots of DEPRECATED stuff
> in the file p-exp.y.
>
> But none of the expression parser is listed in the ARI
> report web page, why is that?
> Wouldn't it be better to include them
> or would it give too many false alarms?
I don't see any of the .y files listed in the ARI. Perhaps the
scripts don't know how to handle YACC grammars.
next prev parent reply other threads:[~2007-07-27 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 11:02 Pierre Muller
2007-07-28 0:02 ` Jim Blandy [this message]
2007-07-31 11:53 ` Pierre Muller
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=m3odhxd98q.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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