Verilog::Parser (* causes error #403
Comments
|
Original Redmine Comment [Usage] On this or most errors, the parser calls the error callback, which defaults (Parser.pm's error) to calls croak. You can thus make your own error callback and override this behavior. |
|
Original Redmine Comment Wilson, fatal flex scanner internal error--end of buffer missed when returning from the error callback. regards, |
|
Original Redmine Comment I poked around a bit trying to fix this, but flex (the lexical analyzer which gives the error) doesn't allow a program to put "back" an EOF so it will be seen later. So unfortunately you won't be able to scan again so if you really want to be bullet proof, you'll need to call your parser under a fork() as a child. |
|
Original Redmine Comment As for the "@(* )" this seems to be legal, and fixed in git towards next release 3.313. |
|
Original Redmine Comment Wilson, Thanks for future fix. As for the fatal exit, I will use a fork/child solution. regards, |
|
Original Redmine Comment In Verilator 3.830. |
|
Original Redmine Comment Still only resolved, not in Verilog-Perl yet. |
|
Original Redmine Comment In 3.313. |
Author Name: Walter Lavino
Original Redmine Issue: 403 from https://www.veripool.org
Original Date: 2011-10-25
Original Assignee: Wilson Snyder (@wsnyder)
Wilson,
( I am using the CPAN Verilog::Parser (+ Verilog::SigParser) )
In my verilog code, I had this statement.
always @ (* ) begin // {
...
end // }
This caused the parser, to see the always parameters
as a comment ( due to space found after the asteriks), than reading until the end of the file and than
calling the $parser->eof() method and
from here it seems exiting the program with message:
"
%Error: filename.v:211: EOF in (*
fatal flex scanner internal error--end of buffer missed
"
However since I am calling the parser in a loop on multiple files
I would like to have the control when the parser actually exits.
Is there anyway or any callback with which I could avoid the exit of my program
and for me to continue my loop ?
So calling the parser like:
$parser->parse_file (shift);
print STDERR "AA\n";
would not print AA
thanks and regards,
Walo
The text was updated successfully, but these errors were encountered: