From: Ralph Corderoy <ralph@inputplus.co.uk>
To: Richard Salz <rich.salz@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] v7 K&R C [really lexers]
Date: Sun, 14 Jun 2020 15:03:03 +0100 [thread overview]
Message-ID: <20200614140303.E5C2A221A1@orac.inputplus.co.uk> (raw)
In-Reply-To: <CAFH29toAeuqaD+gZSf6ijOzHF0C6s1GR2WKQK_WEsk6n_k5omA@mail.gmail.com>
Hi Rich,
> Does anyone have the Usenix paper (80's timeframe I think) about making lex
> go fast? It was by Vern Paxson or Van Jacobson IIRC. Maybe only an
> abstract was published. The talk ended with a chart showing some CPU
> times, and the modified lex was only slightly slower than cat. Maybe Vern
> since he contributed to what became flex.
Google Scholar's ‘Vancouver’ style citation:
Jacobson V. Tuning UNIX Lex or it's NOT true what they say
about Lex. InUSENIX Conference Proceedings (Washington,
DC, Winter 1987) 1987 (pp. 163-164).
Lack of space after ‘In’ is Google, not me.
I didn't find the paper itself, just citations of it.
--
Cheers, Ralph.
next prev parent reply other threads:[~2020-06-14 14:03 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 1:59 [TUHS] v7 K&R C Adam Thornton
2020-04-25 2:37 ` Charles Anthony
2020-04-25 2:47 ` Adam Thornton
2020-04-25 2:51 ` Rob Pike
2020-04-25 2:54 ` Rob Pike
2020-04-25 3:04 ` Larry McVoy
2020-04-25 3:30 ` Clem Cole
2020-04-25 3:43 ` Larry McVoy
2020-04-25 3:54 ` Jon Steinhart
2020-04-25 11:44 ` Michael Kjörling
2020-04-25 13:17 ` Dan Cross
2020-05-11 0:28 ` scj
2020-05-11 0:32 ` Rob Pike
2020-05-11 0:57 ` Larry McVoy
2020-05-11 17:32 ` Greg A. Woods
2020-05-11 18:25 ` Paul Winalski
2020-05-11 18:37 ` Clem Cole
2020-05-11 19:12 ` Paul Winalski
2020-05-11 19:57 ` joe mcguckin
2020-05-11 20:25 ` Larry McVoy
2020-05-12 17:23 ` Paul Winalski
2020-05-12 17:35 ` ron
2020-05-12 17:42 ` Larry McVoy
2020-05-12 18:36 ` Paul Winalski
2020-05-13 23:36 ` Dave Horsfall
2020-05-14 0:42 ` John P. Linderman
2020-05-14 2:44 ` Rich Morin
2020-05-14 3:09 ` Charles Anthony
2020-05-14 12:27 ` ron
2020-05-14 12:27 ` ron
2020-05-14 12:27 ` ron
2020-05-14 7:38 ` Dave Horsfall
2020-05-14 12:25 ` ron
2020-05-14 17:13 ` Paul Winalski
2020-05-14 17:21 ` Larry McVoy
2020-05-17 16:34 ` Derek Fawcus
2020-05-14 4:21 ` Greg A. Woods
2020-05-14 4:40 ` Warner Losh
2020-05-14 17:32 ` Larry McVoy
2020-05-14 22:32 ` Tony Finch
2020-05-16 23:53 ` Steffen Nurpmeso
2020-05-16 23:59 ` [TUHS] v7 K&R C [really lexers] Jon Steinhart
2020-05-17 0:04 ` Brantley Coile
2020-05-17 1:23 ` Warner Losh
2020-05-17 1:36 ` Brantley Coile
2020-06-13 21:24 ` scj
2020-06-14 8:47 ` arnold
2020-06-14 12:52 ` Richard Salz
2020-06-14 14:03 ` Ralph Corderoy [this message]
2020-06-14 14:26 ` arnold
2020-06-14 14:48 ` Ralph Corderoy
2020-06-15 1:12 ` Warren Toomey
2020-06-15 1:29 ` Warren Toomey
2020-06-15 6:06 ` arnold
2020-05-17 16:31 ` Paul Winalski
2020-05-17 0:35 ` [TUHS] v7 K&R C Larry McVoy
2020-05-11 18:37 ` Larry McVoy
2020-05-11 2:08 ` Lawrence Stewart
2020-05-11 11:36 ` Michael Kjörling
2020-04-25 3:37 ` Dave Horsfall
2020-04-27 13:19 ` Tony Finch
2020-04-25 2:50 ` Adam Thornton
2020-04-25 5:59 ` Lars Brinkhoff
2020-05-17 2:07 [TUHS] v7 K&R C [really lexers] Nelson H. F. Beebe
2020-06-14 13:55 Doug McIlroy
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=20200614140303.E5C2A221A1@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--cc=rich.salz@gmail.com \
--cc=tuhs@tuhs.org \
/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).