TokenManager tracing control
Laurent Cerrina
I just wanted to mention that I really enjoy having the enable_tracing and
disable_tracing method in the generated parser. However I would enjoy having
this type of methods available for the tokenmanager. This would be
specially usefull considering the volume of the tokenmanager trace message.
So is there a way to do this with the existing api. If not can we hope for
such an addition to the tokenmanager class.
Sreenivas Viswanadha
> I just wanted to mention that I really enjoy having the enable_tracing and
> disable_tracing method in the generated parser. However I would enjoy having
> this type of methods available for the tokenmanager. This would be
> specially usefull considering the volume of the tokenmanager trace message.
Tracing the methods calls in the token manager is of no use because you cannot
narrow down your problem using that (unlike the parser methods where the method
name is the name of a production). So I don't unserstand what you want this
for.
> So is there a way to do this with the existing api. If not can we hope for
> such an addition to the tokenmanager class.
I don't see its usefulness, so probably we won't support it.
If you wanted a different level of debugging with much less detail that is
something I can think of doing. For example, the lexer can just tell you
what it matched when it returns a token from getNextToken. But I don't
think that information will be useful.
Sreeni.
--
The JavaCC home page is at http://www.sun.com/suntest/products/JavaCC
The latest version of JavaCC is 0.8pre2
The JavaCC FAQ is at http://www.metamata.com/javacc/Faq
Check out the JavaCC newsgroup at comp.compilers.tools.javacc
Send list administration mail to javacc-inte...@metamata.com
Subscribe to javacc-inter...@metamata.com for the digest