Skip Menu |

This queue is for tickets about the GraphViz CPAN distribution.

Report information
The Basics
Id: 36057
Status: resolved
Priority: 0/
Queue: GraphViz

Owner: Nobody in particular
Requestors: tod222 [...]

Bug Information
Severity: Important
Broken in:
  • 2.02
  • 2.03
Fixed in: (no value)

Subject: GraphViz::Parse::RecDescent errors "Error: bad label format"
Running the attached grammar file through GraphViz::Parse::RecDescent results in error messages and broken labels for the corresponding nodes in the resultant graph. Tried with both graphviz 2.16-3ubuntu2 on Ubuntu and 2.12-8.el5 on CentOS/RHEL 5. Error messages: Error: bad label format <port0>gr_out|<port1>'out' '\\{' gr_ofilespec(s) '\\}' \n Error: bad label format <port0>gr_ofilespec|<port1>gr_fileid '\\{' gr_quotedstring gr_identifier(s?) '\\}' \n\<error\> \n Error: bad label format <port0>gr_fielddeclarations|<port1>'\\{' \<leftop: gr_fielddec /;/ gr_fielddec\> gr_code(?) '\\}' \n Error: bad label format <port0>gr_code|<port1>'%\\{' /.+ (?! %\\} \| \\}% )/ _alternation_1_of_production_1_of_rule_gr_code \n Error: bad label format <port0>gr_taskblock|<port1>gr_taskname '\\{' \<commit\> gr_localfields(?) gr_out gr_in(?) gr_do(s) '\\}' \n\<error\> \n Error: bad label format <port0>gr_in|<port1>'in' '\\{' gr_ifilespec(s) '\\}' \n Error: bad label format <port0>gr_ifilespec|<port1>gr_fileid '\\{' gr_quotedstring gr_identifier(s?) '\\}' \n\<error\> \n
Subject: grammar.rules
Download grammar.rules
application/octet-stream 1.4k

Message body not shown because it is not plain text.

Subject: graphviz_grammar
Download graphviz_grammar
application/octet-stream 350b

Message body not shown because it is not plain text.

Download (untitled) / with headers
text/plain 294b
This issue is fixed in GraphViz2 V 1.00. There won't be any more development on GraphViz. I (Ron) have copied you sample grammar into the t/ dir in GraphViz2, so you can run scripts/ as shipped and also patch that script to read the other file t/sample.recdescent.2.dat.

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to