Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!feeds.phibee-telecom.net!usenet.ukfsn.org!not-for-mail From: Martin Gregorie Newsgroups: comp.lang.java.programmer Subject: Re: regexp(ing) Backus-Naurish expressions ... Date: Mon, 11 Mar 2013 23:06:25 +0000 (UTC) Organization: UK Free Software Network Lines: 21 Message-ID: References: NNTP-Posting-Host: 84.45.235.129 Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: localhost.localdomain 1363043185 19791 84.45.235.129 (11 Mar 2013 23:06:25 GMT) X-Complaints-To: usenet@localhost.localdomain NNTP-Posting-Date: Mon, 11 Mar 2013 23:06:25 +0000 (UTC) User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2) Xref: csiph.com comp.lang.java.programmer:22912 On Mon, 11 Mar 2013 22:28:42 +0000, Stefan Ram wrote: > =?UTF-8?B?Sm9zaHVhIENyYW5tZXIg8J+Qpw==?= > writes: >>On 3/10/2013 5:54 PM, Roedy Green wrote: >>>parsing Java >>Actually, all of those examples fall under the category of lexing, > > Parsing is not lexing, usually parsing comes after lexing. When I need to do that in Java I use the Coco/R parser generator. It generates both lexer and parser and IMO is more understandable than the classic C equivalent (Lex + Yacc or Flax + Bison), at least partly because its easy to modify or extend the framework it runs in and the generated code is fairly readable. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |