Re: Insensitive wildcard matching

[Eli Zaretskii]

> Date: Mon, 26 Jul 2004 08:08:11 +0200
> From: Alessandro Vesely <address@hidden>
> 
> IMHO the question is not much what windows OS would be [non-]conformant to,
> but rather if it is misleading or not to allow `echo' to be resolved as
> an internal shell command, but then keep the possibility to issue an `ECHO'
> command that will instead resolve to a non-shell `echo.exe', if one can be
> found on the current PATH.

IMNSHO, Make on Windows should _always_ prefer non-shell echo.exe if
it can be found.  That's because echo.exe's functionality is a
superset of what the Windows shell builtin can do, so you lose
nothing; what you gain is the ability to have Unixy features in
Makefile's.  (If one wants the shell builtin, one can always say
something like "cmd.exe /c echo ...".)

FWIW, the DJGPP (a.k.a. DOS) port of GNU Make works like that, and I
have yet to hear a single complaint.