🚀 go-pugleaf

I don't know if this has been noticed before, but there is a severe problem
with make and Bourne shell scripts.  If the IFS environment variable is set
when make is invoked, then make resets IFS to an empty string.  This almost
guarantees that Bourne shell scripts will die horribly.

To repeat, create an empty directory, cd there, and do:
% /bin/sh
$ cat >foo <<FOO
echo \$#
set "\$@"
echo \$#
FOO
$ chmod +x foo
$ cat >makefile <<FOO
x:	y
	foo 1 2 3
FOO
$ >y
$ foo 1 2 3
3
3
$ IFS=' 	
'
$ # that's IFS='<space><tab><newline>'
$ export IFS
$ foo 1 2 3
3
3
$ make
	foo 1 2 3
3
1
$ ^D
% 

The final "1" output by foo is the error.  The problem is that the
	set "$@"
in foo is being expanded into
	set "1" "2" "3"
which, since IFS is empty (and therefore there are no field seperators),
is interpreted as
	set "1 2 3"
-- i.e., there is just one argument to set.  Needless to say, this causes
some problems.  For example, suppose /bin/cc is a shell script which invokes
the compiler after adding some flags to the comand line:
	#!/bin/sh
	exec /lib/cc -foo -bar "$@"
If IFS is set when make is invoked, and if make invokes cc, then /lib/cc will
be invoked with argc==2, as if it had been invoked by
	exec /lib/cc "-foo -bar $*"

		Fritz Nordby.	fritz@vlsi.caltech.edu	cit-vax!fritz