History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: BOO-471
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Arron Washington
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Boo

boo lexer improvement when dealing with "unexpected" characters

Created: 04/Sep/05 01:05 PM   Updated: 04/Sep/05 01:05 PM
Component/s: Parser
Affects Version/s: 0.6
Fix Version/s: None

Time Tracking:
Not Specified


 Description  « Hide
At the moment, passing "public ! public" to the Boo Lexer currently causes it to throw an exception when the tokenizer reaches the '!' which is good.

However, if you catch the exception and call lexer.nextToken() again, the lexer remains on the unknown character, repeatedly throwing the exception.

Unfortunately this means you are not able to use the Boo Lexer as a cheap-and-easy way to parse documents for important tokens, becaues you cannot step past any invalid tokens that stand between you and great justice.

In my opinion it would be nice if the lexer were able to step "over" bad tokens once they have been first encountered, provided the exception is caught.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.