On 01/21/2010 02:40 PM, Jim Idle wrote:

> You are probably right on the limit of the default 10000, or perhaps
> you are not compiling the exact original?

I haven't touched it.  Honestly!

Besides, the default seems to be 1000, not 10000.  

 $ java -jar Downloads/antlr-3.2.jar -X
  -Xconversiontimeout t   set NFA conversion timeout (ms) for each decision     
     [1000]

I changed it to 10000, and all is fine:

--- 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?

> Try the on in the examples zip and see if there are any
> differences. However, Xeon's are not as fast as you think on a
> single thread which is what the analysis phase runs on by default.

Err, how on Earth do you know how fast I think Xeons are?  :-)
But anyway, most users aren't likely to have anything hugely faster.

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.


Reply via email to