On 07/03/2010 10:14 PM, Matt Palmer wrote:
> I should add, in case the way I phrased the problem is causing any
> confusion: The grammar itself is fine (well - it works - it may not be very
> elegant!). Code can be generated. I have no warnings or errors. The
> problem is whether the debugger in antlrworks will choose to start up, or
> time out.
I had this problem too. The only way seemed to be to edit the source code
of ANTLR to fix the timeout.
--- antlr-3.2/tool/src/main/java/org/antlr/analysis/DFA.java~ 2009-09-23
19:36:06.000000000 +0100
+++ antlr-3.2/tool/src/main/java/org/antlr/analysis/DFA.java 2010-01-21
13:08:32.625782840 +0000
@@ -53,7 +53,7 @@
*/
/** Set to 0 to not terminate early (time in ms) */
- public static int MAX_TIME_PER_DFA_CREATION = 1*1000;
+ public static int MAX_TIME_PER_DFA_CREATION = 10*1000;
/** How many edges can each DFA state have before a "special" state
* is created that uses IF expressions instead of a table?
The core problem was that antlrworks didn't allow this timeout to be
tweaked.
Andrew.
List: http://www.antlr.org/mailman/listinfo/antlr-interest
Unsubscribe:
http://www.antlr.org/mailman/options/antlr-interest/your-email-address
--
You received this message because you are subscribed to the Google Groups
"il-antlr-interest" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/il-antlr-interest?hl=en.
