[antlr-interest] ANTLR equivalent of JavaCC Lexer behaviour?

PATERSON, Robert r.paterson at ioof.com.au
Mon Mar 27 16:11:51 PST 2006

Well, my ANTLR experience is limited to knocking out some pretty
straight forward parsers, so I wouldn't draw any conclusions from
anything I say! 

-----Original Message-----
From: antlr-interest-bounces at antlr.org
[mailto:antlr-interest-bounces at antlr.org] On Behalf Of
Richard.Kennard at mail.thomson.com
Sent: Tuesday, 28 March 2006 11:09 AM
To: antlr-interest at antlr.org
Subject: RE: [antlr-interest] ANTLR equivalent of JavaCC Lexer


Fair enough.

So would I be right in thinking that the JavaCC Lexer is implemented
quite differently? That there is no ANTLR equivalent (either now or
planned, though I guess that is a question for Ter)?



This communication is intended only for the use of the addressee and 
may contain personal information, confidential information or legally 
privileged information. If personal information is contained in this e-mail, 
then it is governed by the Privacy Act 1988 and must be treated in 
accordance with the Privacy Act 1988 by the recipient. The legal 
privilege and confidentiality attached to this e-mail is not waivered, 
lost or destroyed by reason of mistaken delivery to you. If you are not 
the intended recipient, we would appreciate immediate notification by 
return e-mail or telephoning +61-3-8614-4444 and ask that the message 
be permanently deleted from your system. If you are the intended 
recipient of this communication you should not copy, disclose or distribute this communication without the authority of IOOF or its related entities (the IOOF Group).
Any views expressed in this message are those of the individual sender, 
except where they are specifically stated to be the views of the IOOF 
This e-mail and any attachments have been scanned for computer viruses 
using anti-viral software, but you should also perform your own scan. We 
do not accept liability for any loss or damage, whether caused by our own negligence or not, that results from a computer virus or a defect in the transmission of the e-mail or any attached file.

More information about the antlr-interest mailing list