[antlr-interest] java.g does not compile

[Jim Idle]

They probably would, unless they read the comments at the start of the .g file, where it says:

*  NOTE: If you try to compile this file from command line and Antlr gives an exception 
*    like error message while compiling, add option 
*    -Xconversiontimeout 100000
*    to the command line.  

Sorry - missed the Nehalem comment. However, my 3Ghz QX9650 (forgot what CPU I had in this thing) running Vista 64 and Sun's 64 bit JRE deals with it just fine.

Jim

> -----Original Message-----
> From: antlr-interest-bounces at antlr.org [mailto:antlr-interest-
> bounces at antlr.org] On Behalf Of Andrew Haley
> Sent: Thursday, January 21, 2010 7:23 AM
> To: antlr-interest at antlr.org
> Subject: Re: [antlr-interest] java.g does not compile
> 
> On 01/21/2010 03:00 PM, Jim Idle wrote:
> 
> > I wouldn't change the default time out as then your project depends
> > on a custom version of NATLR for no good reason. That was just my
> > 6:40AM typo of course :-)
> 
> I'm using antlrworks, and I can't find any other way to change the
> default.
> 
> > I have a QX9450 and some i7s. I think that the Xeon server versions
> > of 9450 etc might be slower on a single thread.
> 
> I'm sure they would be, but I'm talking about a Nehalem-based Xeon: it
> *is* an i7, not a Core 2 anything.  The Xeon 35xx and Core i7-9xx are
> more or less the same thing.
> 
> So, I think that almost everyone would have the same problem I'm
> having.
> 
> Andrew.
> 
> List: http://www.antlr.org/mailman/listinfo/antlr-interest
> Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-
> email-address