Clint Adams dixit: >Again, I read […] >as invalidating your "either-or" mandate.
Indeed, I concede, I’ve read something recently supporting that view. Pity though, as there’s nothing reasonably wide-spread that is guaran- teed to not expand them (printf(1) is problematic, not the least since it lives in /tmp). Autoconf uses echo X"$string" | sed -e 's/^X//' -e 〈transform〉 to transform a string. There be dangers, etc. My concern was haserl, which is similar to php, except it basically wraps everything between <? and ?> into echo -n '...' blocks. Should be fixed in haserl, then. (Nevertheless, I made mksh-as-/bin/sh’s echo haserl-friendly.) bye, //mirabilos -- Sometimes they [people] care too much: pretty printers [and syntax highligh- ting, d.A.] mechanically produce pretty output that accentuates irrelevant detail in the program, which is as sensible as putting all the prepositions in English text in bold font. -- Rob Pike in "Notes on Programming in C" -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
