From: mah@mhorton.net (Mary Ann Horton)
Subject: [TUHS] Short history of 'grep'
Date: Sun, 31 Jan 2016 09:11:05 -0800 [thread overview]
Message-ID: <56AE4029.7010701@mhorton.net> (raw)
In-Reply-To: <alpine.LRH.2.20.1601301802360.8927@waffle.shalott.net>
It's not a typo.
When I tell this story to nontechical folks, I prefix it with the brief
note that fgrep ought to be fastest, because it's simple, and egrep
ought to be slowest, because it's complex, but in reality fgrep is
slowest and egrep is fastest. Otherwise the story makes no sense.
Mary Ann
On 01/30/2016 06:06 PM, jason-tuhs at shalott.net wrote:
>
>> I'm still trying to get my around about how a program such as "egrep"
>> which handles complex patterns can be faster than one that doesn't...
>> It seems to defeat all logic :-)
>>
>> Is there a simple explanation, involving small words? I've never
>> really looked at the theory.
>
> My assumption when I read it was that it was a typo/braino, that the
> intent was "fgrep" rather than "egrep".
>
>
> -Jason
>
next prev parent reply other threads:[~2016-01-31 17:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2016-01-31 17:01 Doug McIlroy
2016-03-05 1:48 ` Dave Horsfall
2016-03-05 1:54 ` Larry McVoy
2016-02-01 20:57 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=56AE4029.7010701@mhorton.net \
--to=mah@mhorton.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).