From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] Short history of 'grep'
Date: Sat, 5 Mar 2016 12:48:19 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.11.1603051235320.89489@aneurin.horsfall.org> (raw)
In-Reply-To: <201601311701.u0VH12It027916@coolidge.cs.Dartmouth.EDU>
On Sun, 31 Jan 2016, Doug McIlroy wrote:
[...]
> That's the short story. In real life egrep overcomes the exponential by
> lazily constructing the machine--not generating a state until it is
> encountered in the parse, so no more than n states get constructed. It's
> a complex program, though, for the already fancy preprocessing must be
> interleaved with the parsing.
Many thanks; I think I understand a little better now... It's been many
years since I majored in Computer Science :-)
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2016-03-05 1:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 17:01 Doug McIlroy
2016-03-05 1:48 ` Dave Horsfall [this message]
2016-03-05 1:54 ` Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
2016-02-01 20:57 Doug McIlroy
2016-01-30 3:00 Warren Toomey
2016-01-30 19:10 ` Mary Ann Horton
2016-01-30 19:44 ` Dave Horsfall
2016-01-30 20:20 ` Mary Ann Horton
2016-01-30 20:40 ` Dave Horsfall
2016-01-30 21:42 ` Marc Rochkind
2016-01-31 1:41 ` Dave Horsfall
2016-01-31 1:50 ` Larry McVoy
2016-01-31 2:06 ` jason-tuhs
2016-01-31 4:20 ` Random832
2016-01-31 17:11 ` Mary Ann Horton
2016-01-31 17:38 ` John Cowan
2016-02-01 10:48 ` Tony Finch
2016-01-31 2:37 ` John Cowan
2016-02-01 10:38 ` Tony Finch
2016-02-01 19:26 ` scj
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=alpine.BSF.2.11.1603051235320.89489@aneurin.horsfall.org \
--to=dave@horsfall.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).