Keith Marshall <keithmarshall@xxxxxxxxxxxxxxxxxxxxx> writes: > Let me turn that around, and ask if you can provide any documentary > evidence, other than anecdotal, to suggest that this use of semicolons > *should* be supported? SUSv3 *expressly* demands that sed directives be > separated by newlines: > http://www.opengroup.org/onlinepubs/009695399/utilities/sed.html "The command can be preceded by <blank>s and/or semicolons. The function can be preceded by <blank>s. These optional characters shall have no effect." "Command verbs other than {, a, b, c, i, r, t, w, :, and # can be followed by a semicolon, optional <blank>s, and another command verb." Andreas. -- Andreas Schwab, SuSE Labs, schwab@xxxxxxx SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
