[antlr-interest] parsing performance

Mark Johnson msjohnson at attbi.com
Wed Sep 11 19:35:44 PDT 2002

While you are considering constructors how about adding a constructor which
accepts either a string or a byte array?  This would save me from having to
convert a string into a ByteArrayInputStream.


-----Original Message-----
From: Terence Parr [mailto:parrt at jguru.com]
Sent: Monday, September 09, 2002 2:00 AM
To: antlr-interest at yahoogroups.com
Subject: Re: [antlr-interest] parsing performance

On Sunday, September 8, 2002, at 10:02  PM, John D. Mitchell wrote:
>>>>>> "Terence" == Terence Parr <parrt at jguru.com> writes:
> [...]
>> Also note that 1.4 java is supposed to be much faster at IO than 1.3
>> and
>> before.  Let's hope ;)
> To be clear, Java v1.4 supports a number of I/O improvements in the
> "nio"
> (New I/O) package (such as memory-mapped files).
> Those changes have *NOT* yet been incorporated into the old, standard
> Java
> I/O packages.  That might happen for Java v1.5.
> So, any code that y'all want to make faster by taking advantage of the
> new
> I/O support has to be rewritten.

Ouch.  Dang!  I'll look at the API, but this is something we could use
by making a new constructor on the lexer to take a different kind o
stream, right?

Co-founder, http://www.jguru.com
Creator, ANTLR Parser Generator: http://www.antlr.org

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 

More information about the antlr-interest mailing list