Paul Eggert wrote: > Autoconf is littered with code like this: > > ac_script='s/\$U\././;s/\.o$//;s/\.obj$//' > ac_i=`echo "$ac_i" | sed "$ac_script"` > > This passes an argument with two trailing slashes to 'sed'. > Does it misbehave too, under OSF/Tru64 5.1? It cannot possibly and if it did, then you gotta test for it, then choke and die. The slashes are all protected with quotes. Were the last line to read: > ac_i=`echo "$ac_i" | sed $ac_script` you would have a different situation. Do those different situations exist? > The bug seems to be pretty fundamental; I'm not sure it's worth coding > around. But if it is, then here's a proposed patch to the autoconf > manual. No. Don't code around it. Autoconf is slow enough. :-) Cheers - Bruce
