AC_PROG_EGREP behaviour

[Stepan Kasal]

Hello,
  the behaviour of AC_PROG_EGREP has changed.  I'd like to ask whether
this was intentional.

Previously, the macro set EGREP=egrep even if there was no egrep on the
system.
The CVS version calls _AC_PROG_GREP, which means that on system without
any working egrep, configuration halts with an error.  Is that OK?

OTOH, if AC_PROG_AWK finds no awk, the variable AWK is not set.
Shouldn't we halt with an error too?
Or shouldn't we set AWK=awk anyway, similarily to AC_PROG_YACC?

Shouldn't the documentation of AC_PROG_{AWK,*GREP,SED} mention these
issues?

Have a nice day,
        Stepan