31 Jan
2016
31 Jan
'16
11:11 p.m.
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(a)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