Grammatica - Bugs: bug #8601, Add --verbose output flag to track...
You are not allowed to post comments on this tracker with your current authentication level.
bug #8601: Add --verbose output flag to track grammar preparation
Submitter: | Per Cederberg <cederberg> | ||
Submitted: | Fri 16 Apr 2004 10:40:57 PM UTC | ||
Severity: | 5 - Major | Item Group: | Future Improvement |
Status: | None | Assigned to: | cederberg |
Open/Closed: | Open |
Attached Files
file #1216: jml.orig.grammar added by cederberg (30KiB - application/octet-stream - An example grammar file causing the problematic behaviour)
Depends on the following items: None found
Items that depend on this one: None found
CC list is empty
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2004-04-16 | cederberg | Attached File | - | Added jml.orig.grammar, #1199 |
Powered by Savane 3.13-f8d8.
Corresponding source code
When creating a parser, look-ahead sets are calculated for all productions in the grammar. Normally this is a reasonably quick operation, but in some extreme cases it can be very slow due to inherent ambiguities in combination with a combinatorial explosion. When look-ahead sets starts growing to sizes of more than a thousand entries, the look-ahead calculation in general slows down to a crawl.
Currently the --debug mode and others do not print anything during this phase, which leads the user into thinking that Grammatica has entered an infinite loop. This should be remedied by either changing the --debug mode to print information on conflicts while the look-ahead calculation is being done, or by adding a new --verbose flag that causes such printouts to occur.