Grammatica - Bugs: bug #4500, Parser: Several runs should be...
You are not allowed to post comments on this tracker with your current authentication level.
bug #4500: Parser: Several runs should be possible with a single parser instance
Submitter: | Per Cederberg <cederberg> | ||
Submitted: | Sun 27 Jul 2003 02:19:15 PM UTC | ||
Severity: | 5 - Major | Item Group: | Future Improvement |
Status: | Fixed | Assigned to: | cederberg |
Open/Closed: | Closed |
Discussion locked!
Sat 14 Mar 2009 09:35:31 AM UTC, comment #2: |
Per Cederberg <cederberg>![]() ![]() |
Thu 22 Apr 2004 10:04:12 PM UTC, comment #1: New reset() methods have been added to the Parser and Tokenizer classes. The Tokenizer internals had to be heavily modified, though, breaking out the character buffer into a new LookAheadReader class. The only API breakage resulting from this was in the regular expression classes, where the match method can now throw an IOException while matching an input stream. When matching normal strings this exception can be ignored (apart from the compilation error it may cause under Java).
|
Per Cederberg <cederberg>![]() ![]() |
Sun 27 Jul 2003 02:19:15 PM UTC, original submission:
A single parser instance should be possible to use for parsing several files, something not allowed by the current API. The current solution is ineffective when parsing several files through the same parser, as the look-ahead token sets must be calculated again every time a parser is created (i.e. every time a file is parsed).
|
Per Cederberg <cederberg>![]() ![]() |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
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.
Version 1.5 was released on 2009-03-07. Closing this issue.