Hopefully the dev group will consider refactoring the code so that when its doing the lexing it will throw TokenMgrException's instead of TokenMgrError's. Throwing Errors should be reserved for only the most nasty of conditions. The compiler will force you to catch or throw Exceptions, but not Errors. Thus, the developer will never see it coming when their application comes to a grinding halt.
I'm not sure I understand your request. With the latest codebase you will only ever get a ParseException coming from either of the parse methods and you don't have to worry about any other unchecked exceptions.
Am I missing something?
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
