9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Replacements for lex
Date: Fri, 19 Jan 2007 14:13:40 -0500	[thread overview]
Message-ID: <312c73e5b2edd1e464cb971a39bd334e@coraid.com> (raw)
In-Reply-To: <7871fcf50701191058w7ef924cer224b9c8e4f63321b@mail.gmail.com>

My suggestion is just to write scanners by hand.  I've written dozens
and they take only a few minutes.  While a half hour seems long
compared to the speed of an automaticly generated scanner, the time
difference over the total project is quite small.  And besides.  You
want to learn how to write compilers.


> Has anyone had success with lexer-generators other than lex under Plan
> 9?  I'm taking a compilers class this semester and I'd like to do as
> much work under Plan 9 as possible.
>
> I looked around online and found re2c, which looked interesting except
> it's written in C++.
>
> For languages sufficiently like C, is regexp(2) suitable?
>
> --Joel



  parent reply	other threads:[~2007-01-19 19:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 18:58 Joel Salomon
2007-01-19 19:12 ` Dan Cross
2007-01-19 19:26   ` Joel Salomon
2007-01-19 20:35     ` C H Forsyth
2007-01-19 21:06       ` erik quanstrom
2007-01-19 21:09       ` Taj Khattra
2007-01-19 21:18         ` Brantley Coile
2007-01-20  8:47     ` William Josephson
2007-01-20  9:08       ` Bruce Ellis
2007-01-19 19:13 ` Brantley Coile [this message]
2007-01-19 19:18 ` erik quanstrom
2007-01-19 19:24   ` Federico Benavento
2007-01-20  8:44 ` William Josephson

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=312c73e5b2edd1e464cb971a39bd334e@coraid.com \
    --to=brantley@coraid.com \
    --cc=9fans@cse.psu.edu \
    /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).