On 7 Feb 1999, 10:00, "Laurent Cerrina" <benoit.cerr...@[EMAIL PROTECTED]
>
wrote:
http://groups.google.com/group/comp.compilers.tools.javacc/browse_thread/thread/fdba27f8670f3286/9689caf002566d2a?lnk=gst&q=tracing&rnum=1#9689caf002566d2a
(that thread is closed to replies, let me continue here)
> Hi,
> 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.
Hi all
Given the current options in the Gpl.jj
options
{
STATIC = true;
UNICODE_INPUT = true;
}
and the default values for the options such as DEBUG_PARSER (false),
DEBUG_TOKEN_MANAGER (false, cf.
https://javacc.dev.java.net/doc/javaccgrm.html#prod2),
nonetheless I note that in the console tab of the Eclipse, calls to
productions (e.g to the Id() production), while unit testing, produce
a lot of tracing messages such as
Call: Id
Consumed token: <<GROUP_ID>>: "a_given_string" at line 1 column 1>
Return: Id
I tried to add an explict call to disable_tracing() in tyhe Id()
production
String
Id() :
{
Token lToken;
String lResult;
disable_tracing();
}
{
lToken = <GROUP_ID>
...
and actually that tracing is switched off.
Default values for DEBUG_PARSER and DEBUG_TOKEN_MANAGER seem not to
work.
What's wrong?
Thanks in advance for any help.
ciao
Cesare
|
