Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Verilog-Perl CPAN distribution.

Report information
The Basics
Id: 27599
Status: rejected
Priority: 0/
Queue: Verilog-Perl
People
Owner: Nobody in particular
Requestors: jetrull [...] sbcglobal.net
Cc:
AdminCc:
Bug Information
Severity: Important
Broken in: 3.000
Fixed in: (no value)

History Show all quoted text
  Fri Jun 15 21:24:52 2007 jetrull [...] sbcglobal.net - Ticket created
Subject: SigParser now rejects `ifdef
SigParser previously ignored `ifdef statements in files it parsed, but now produces this message: Define or directive not defined: `ifdef and terminates the calling script. The previous behavior is more desirable because my use of SigParser is chiefly to collect module port information, and embedded ifdef/endif sections in the code are not really an issue.
  Mon Jun 18 14:21:57 2007 wsnyder [...] wsnyder.org - Correspondence added
On Fri Jun 15 21:24:52 2007, jetrull wrote: Show quoted text
> SigParser previously ignored `ifdef statements in files it parsed, but > now produces this message:
I'm not sure how to fix this. I can easily add something to just ignore all `{anythings} but this is insufficient, as the word after `ifdef will get fed to the parser and it will blow up. The new parser unfortunately needs to have fully valid syntax. Is there a reason why you can't just use the preprocessor?
  Mon Jun 18 14:21:59 2007 The RT System itself - Status changed from 'new' to 'open'
  Mon Jun 18 15:48:37 2007 jeff.trull [...] alumni.cmu.edu - Correspondence added
Subject: Re: [rt.cpan.org #27599] SigParser now rejects `ifdef
Date: Mon, 18 Jun 2007 12:47:32 -0700
To: bug-Verilog-Perl [...] rt.cpan.org
From: Jeff Trull <jetrull [...] sbcglobal.net>
OK, using the preprocessor fixed this. Thanks! On Monday 18 June 2007 11:21:59 via RT wrote: Show quoted text
> <URL: http://rt.cpan.org/Ticket/Display.html?id=27599 > > > On Fri Jun 15 21:24:52 2007, jetrull wrote:
> > SigParser previously ignored `ifdef statements in files it parsed, but > > now produces this message:
> > I'm not sure how to fix this. I can easily add something to just ignore > all `{anythings} but this is insufficient, as the word after `ifdef will > get fed to the parser and it will blow up. The new parser unfortunately > needs to have fully valid syntax. > > Is there a reason why you can't just use the preprocessor?
  Tue Jun 19 15:49:02 2007 wsnyder [...] wsnyder.org - Status changed from 'open' to 'rejected'