Related articles |
---|
recommendation for a WinNT/95 parser generator kgeorge@itchy.serv.net (1997-08-16) |
Re: recommendation for a WinNT/95 parser generator edjaggard@usa.net (1997-08-20) |
Re: recommendation for a WinNT/95 parser generator mtiomkin@iil.intel.com (Michael Tiomkin) (1997-08-24) |
Re: recommendation for a WinNT/95 parser generator kgeorge@itchy.serv.net (1997-08-28) |
recommendation for a WinNT/95 parser generator Robert.M.Muench@SCRAP.de (Robert M. Muench) (1997-08-30) |
Re: recommendation for a WinNT/95 parser generator dwight@pentasoft.com (Dwight VandenBerghe) (1997-08-30) |
Re: recommendation for a WinNT/95 parser generator jlilley@empathy.com (John Lilley) (1997-08-30) |
Re: recommendation for a WinNT/95 parser generator andrewc@rosemail.rose.hp.com (Andrew Crabtree) (1997-08-30) |
Re: recommendation for a WinNT/95 parser generator dweller@news.imagin.net (1997-09-03) |
From: | John Lilley <jlilley@empathy.com> |
Newsgroups: | comp.compilers |
Date: | 30 Aug 1997 00:51:34 -0400 |
Organization: | Nerds for Hire, Inc. |
References: | 97-08-061 97-08-069 97-08-076 |
Keywords: | i18n, lex |
Koshy George wrote:
> unicode-input is another requirement. So far I have not found, any
> parser generator which produce parser/lexer who accepts their tokens
> as unicode characters(16 bits), or multibyte chars.
You may want to check out JavaCC from Sun. LL(k) parser, DFA lexer.
Generates Java.
ANTLR 2.0 does not yet support UNICODE, but could do so in theory as
soon as Terence or myself get some more time. The only thing missing is
a UTF-to-UNICODE front-end and a sparse bitset. ANTLR 2.0 is LL(k)
lexer, LL(k) parser. Generates Java.
john
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.