Installation notes
==================

egrep and fgrep both require the presence of grep somewhere on Run$Path (eg.
in !Boot.Library, or in the current directory); they are merely launchers
which load the grep executable and jump to its start.


Usage
-----

You won't notice the difference between this implementation and the
alternative of having three similarly-sized executables.


Other notes
-----------

The egrep and fgrep executables themselves are identical. The differentiation
is in the names; each will load grep in such a way as to preserve the command
line which was passed to it, and grep will pick this up and read the leafname
of the file which was run, using it to determine the (initial) mode - whether
it's run as grep, egrep or fgrep.

This auto-detection makes much more sense than the original method, which
produces three near-identical executables, the only differences being in one
hard-wired string :-)

(It also means that the archive is that much smaller, and that I only have to
rebuild one executable...)


-- 
Darren Salt
