The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rich Salz <rich.salz@gmail.com>
To: John Levine <johnl@taugh.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: parsing tools, was What would early alternatives
Date: Tue, 11 Mar 2025 22:22:00 -0400	[thread overview]
Message-ID: <CAFH29tr-ftcehn=HyWddh73Ao-sDaPj9XP33bCf8rYoPuMWx3A@mail.gmail.com> (raw)
In-Reply-To: <vqqoe9$2vd1$1@gal.iecc.com>

[-- Attachment #1: Type: text/plain, Size: 961 bytes --]

>
> Lex was a dog. Flex, which as far as I know was a complete rewrite
> that shared no code with lex, are not bad.
>

Yes, "it's true what they say about lex" was a common phrase.  (I think I
first saw it in the pathalias paper.)

There was a Usenix presentation -- late 80's (Washington?) but I couldn't
find it. -- by Vern Paxson about his rewrite called flex. I think he said
that the main reason lex was slow was the clever folding it had to do of
its internal tables to fit. Sadly Vern never got his paper in, but the
presentation showed a group with three lines, one at the top being slow
lex, the next two much lower on the Y axis being very close. He said the
second line was flex. Someone said what about the third, fastest, line? His
answer "that's cat"

Vern worked with Van on early network improvements (web-search the both of
them for a fun time).

Flex first posted to Usenet in 1988,
https://groups.google.com/g/comp.sources.unix/c/LZ_EHqd7XBg

[-- Attachment #2: Type: text/html, Size: 1386 bytes --]

  reply	other threads:[~2025-03-12  2:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-10  2:03 [TUHS] Re: What would early alternatives to C have been? Douglas McIlroy
2025-03-10  2:28 ` Charles H. Sauer
2025-03-11  2:26   ` [TUHS] Re: uphill both ways, was " John Levine
2025-03-10  4:10 ` [TUHS] " Rob Pike
2025-03-10 15:19   ` John Cowan
2025-03-10 19:56     ` Dave Horsfall
2025-03-10 20:49     ` Bakul Shah via TUHS
2025-03-10 23:12       ` Marc Rochkind
2025-03-10 23:49         ` Clem Cole
2025-03-10 23:58           ` Marc Rochkind
2025-03-11  0:06           ` Ken Thompson
2025-03-11  1:35             ` Larry McVoy
2025-03-11  5:07               ` Ken Thompson
     [not found]         ` <CAKH6PiW8J8=uFbadUTSaC9VcLGUJMFZaSFWOFDyCM3MpMTSayw@mail.gmail.com <CAMP=X_mchJuVgdpc4-AYHASwEVzUcJXMmqSDv_UvX6y0o0+LBQ@mail.gmail.com>
2025-03-12  1:36           ` [TUHS] Re: parsing tools, was What would early alternatives John Levine
2025-03-12  2:22             ` Rich Salz [this message]
2025-03-12  3:35               ` Larry McVoy
2025-03-12 16:35               ` John R Levine
2025-03-12  5:11             ` Greg A. Woods
2025-03-11  5:15       ` [TUHS] Re: What would early alternatives to C have been? John Cowan
2025-03-10 15:12 ` Clem Cole
2025-03-10 15:24   ` Dan Cross

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='CAFH29tr-ftcehn=HyWddh73Ao-sDaPj9XP33bCf8rYoPuMWx3A@mail.gmail.com' \
    --to=rich.salz@gmail.com \
    --cc=johnl@taugh.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).