apenwarr-redo/t/110-compile/CC.do

exec >$3
cat <<-EOF
	cc -Wall -o /dev/fd/1 -c "\$1"
EOF
chmod a+x $3
$3 and stdout no longer refer to the same file. This is slightly inelegant, as the old style echo foo echo blah chmod a+x $3 doesn't work anymore; the stuff you wrote to stdout didn't end up in $3. You can rewrite it as: exec >$3 echo foo echo blah chmod a+x $3 Anyway, it's better this way, because now we can tell the difference between a zero-length $3 and a nonexistent one. A .do script can thus produce either one and we'll either delete the target or move the empty $3 to replace it, whichever is right. As a bonus, this simplifies our detection of whether you did something weird with overlapping changes to stdout and $3. 2010-12-11 00:29:04 -08:00			`exec >$3`
Extremely basic first crack at implementing djb's redo. And a test program. 2010-11-12 05:24:46 -08:00			`cat <<-EOF`
Tests: use cc instead of gcc. This fixes problems where llvm is installed without a 'gcc' alias. 2018-10-29 07:20:33 +00:00			`cc -Wall -o /dev/fd/1 -c "\$1"`
Extremely basic first crack at implementing djb's redo. And a test program. 2010-11-12 05:24:46 -08:00			`EOF`
			`chmod a+x $3`