<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>I have noticed some strange behaviour in ANTLRWorks
recently. This has only started happening in the past week and has pretty
much baffled me. It seems as though ANTLRWorks is no longer printing out
reported errors during debug. When encountering a mismatched, unviable
alt or other recognition exception, the expected behaviour is to report the
error to the console, similar to:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=red face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:red'>line 3:1
extraneous input 't' expecting NEWLINE<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=red face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:red'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:black'>When I first started using ANTLRWorks, I
would regularly test my grammar by running the debug feature to ensure it would
recognize and report such syntax errors and it did. Now, after nothing
notable has changed (only minor edits to the grammar), ANTLRWorks no longer
reports these error messages to the ‘output’ debug console even
though a recognition exception can clearly be seen while tracing through both
the event stack and parse tree. What is more strange, when I generate the
code and test the parser class within Eclipse, the expected syntax error
messages <b><i><span style='font-weight:bold;font-style:italic'>are </span></i></b>printed
to the console. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:black'>I attempted to troubleshoot this issue
for an afternoon and have now turned to the community to see whether anyone
else has experienced strange behaviour such as this from ANTLRWorks or what
might be causing it. I have not changed anything in the way the grammar
handles errors and the standard catch clause should simply report and recover
from the error. This happens in Eclipse but not in ANTLR debug.
Anyone seen anything like this?<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:black'>Dave<o:p></o:p></span></font></p>
</div>
</body>
</html>