Related articles |
---|
[2 earlier articles] |
Re: is lex useful? rkanagy@erols.com (Ronald Kanagy) (1996-06-23) |
Re: is lex useful? qjackson@direct.ca (1996-06-24) |
Re: is lex useful? kelley@Phys.Ocean.Dal.Ca (1996-06-24) |
Re: is lex useful? Scott.Nicol@infoadvan.com (1996-06-24) |
Re: is lex useful? kanze@lts.sel.alcatel.de (1996-06-24) |
Re: is lex useful? bos@serpentine.com (1996-06-26) |
Re: is lex useful? dhami@mdd.comm.mot.com (1996-06-26) |
Re: is lex useful? stefan.monnier@lia.di.epfl.ch (Stefan Monnier) (1996-06-26) |
Re: is lex useful? raph@kiwi.cs.berkeley.edu (1996-06-26) |
Re: is lex useful? rgreen@barach.bbn.com (1996-06-26) |
Re: is lex useful? leichter@smarts.com (Jerry Leichter) (1996-06-27) |
Re: is lex useful? scooter@mccabe.com (Scott Stanchfield) (1996-06-27) |
Re: is lex useful? Scott.Nicol@infoadvan.com (1996-06-27) |
[14 later articles] |
From: | dhami@mdd.comm.mot.com (Mandeep S Dhami) |
Newsgroups: | comp.compilers |
Date: | 26 Jun 1996 11:38:16 -0400 |
Organization: | Motorola - Wireless Data Group; Richmond, BC |
References: | 96-06-073 96-06-105 |
Keywords: | lex, comment |
Scott.Nicol@infoadvan.com (Scott Nicol) writes:
>- Parser-scanner interactions can get really hairy (a common way to fix
> difficult parsing problems is to have the parser fiddle with the scanner,
> so the scanner will handle it).
IMHO, This is by far the most important reason to write your own lexer.
You can often simplified yacc grammar by doing this. To some this may be
"bad" design (wrong use of tools/inappropiate coupling), to others, it is
"smart" design! Anyway, I feel the later.
Regards,
Mandeep
---------------------------------------------------------------------------
Mandeep S Dhami
Motorola Wireless Data Division Email: dhami@mdd.comm.mot.com
11411 Number Five Road Office: (604) 241-6334
Richmond, BC, Canada V7 A4 Z3 Fax: (604) 241-6042
[I've never had any trouble putting gross hacks into my flex lexers using
start states. I'd be interested in examples of scanner hackery that's hard
in flex but easy in a hand-coded lexer. -John]
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.