From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Config File parsing
Date: Tue, 28 Feb 2012 08:46:33 -0800 [thread overview]
Message-ID: <6111913F-25EB-4182-8E3B-357446F05655@bitblocks.com> (raw)
In-Reply-To: <CAEE9J-UHo=5fnWF2FA_u+AUwPVz9LuUx7_V_rv8cYU7hmG_iBg@mail.gmail.com>
I have almost always used a handwritten lexer as it seemed about the same amount of work and the end result is much smaller and easier to understand and lexers for different languages are not all that different so once you've written one it is pretty easy to write another; and somehow lex or flex interface never felt quite right.
On Feb 27, 2012, at 8:03 PM, Nick LaForge <nicklaforge@gmail.com> wrote:
> Are you certain you want to use Lex? If no, you may like this
> fascinating and instructive lecture by Rob Pike, which solves a lexing
> problem using Golang: http://www.youtube.com/watch?v=HxaD_trXwRE
>
> If you have "The Unix Programming Environment" handy, you will also
> find a lucid tutorial of Lex and Yacc both (in the later chapters).
>
> Nick
>
> On 2/27/12, arnold@skeeve.com <arnold@skeeve.com> wrote:
>> O'Reilly's "lex & yacc" is somewhat more user-friendly a reference than
>> the dragon book, although the latter certainly has its value. :-)
>>
>> Arnold
>>
>>
>
next prev parent reply other threads:[~2012-02-28 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 13:23 arnold
2012-02-28 4:03 ` Nick LaForge
2012-02-28 14:57 ` Aram Hăvărneanu
2012-02-28 16:46 ` Bakul Shah [this message]
2012-02-28 16:57 ` erik quanstrom
[not found] <199d7d8a-c02f-4b21-bb9b-c9be189024bc@w27g2000yqm.googlegroups.co>
2012-02-27 13:18 ` erik quanstrom
2012-02-27 14:06 ` Jack Norton
-- strict thread matches above, loose matches on Subject: below --
2012-02-27 9:53 Mohanasundaram VIT
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6111913F-25EB-4182-8E3B-357446F05655@bitblocks.com \
--to=bakul@bitblocks.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).