Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Jim Blandy'" <jimb@codesourcery.com>
Cc: <gdb@sourceware.org>
Subject: RE: Question about ARI for expression parsers
Date: Tue, 31 Jul 2007 11:53:00 -0000	[thread overview]
Message-ID: <002c01c7d348$b358dd40$1a0a97c0$@u-strasbg.fr> (raw)
In-Reply-To: <m3odhxd98q.fsf@codesourcery.com>

  I big part of the YACC grammar files
are in fact C functions like yylex,
and those would certainly benefit from
being checked as usual C sources are.

  Nervertheless, I did not look into the
scripts used to generate these ARI reports
and have no clue if it would be feasible/easy
to restrict the checking to the included
C functions, or if treating the whole
file as a C source would generate errors,
or false reports.

  If someone could try to add the yacc grammar sources
and report the results, we might get an idea if 
there is more work needed to insert these files
into the ARI report.

Pierre Muller

> -----Original Message-----
> From: Jim Blandy [mailto:jimb@codesourcery.com]
> Sent: Friday, July 27, 2007 7:53 PM
> To: Pierre Muller
> Cc: gdb@sourceware.org
> Subject: Re: Question about ARI for expression parsers
> 
> 
> "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.




      reply	other threads:[~2007-07-31  7:59 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
2007-07-31 11:53   ` Pierre Muller [this message]

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='002c01c7d348$b358dd40$1a0a97c0$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=gdb@sourceware.org \
    --cc=jimb@codesourcery.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