From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24172 invoked by alias); 31 Jul 2007 07:59:28 -0000 Received: (qmail 24164 invoked by uid 22791); 31 Jul 2007 07:59:28 -0000 X-Spam-Check-By: sourceware.org Received: from ics.u-strasbg.fr (HELO ics.u-strasbg.fr) (130.79.112.250) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 31 Jul 2007 07:59:26 +0000 Received: from ICSMULLER (unknown [130.79.244.145]) by ics.u-strasbg.fr (Postfix) with ESMTP id DFBD218701C; Tue, 31 Jul 2007 10:03:11 +0200 (CEST) From: "Pierre Muller" To: "'Jim Blandy'" Cc: References: <002d01c7d02f$11e9e510$35bdaf30$@u-strasbg.fr> In-Reply-To: Subject: RE: Question about ARI for expression parsers Date: Tue, 31 Jul 2007 11:53:00 -0000 Message-ID: <002c01c7d348$b358dd40$1a0a97c0$@u-strasbg.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Content-Language: en-us Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-07/txt/msg00219.txt.bz2 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" 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.