Fix Posix-conformance bugs re use of { command in sed scripts,
commit0ee621917ab67f0f51c90455bd605fabae181566
authorPaul Eggert <eggert@cs.ucla.edu>
Thu, 5 Jan 2006 21:43:44 +0000 (5 21:43 +0000)
committerPaul Eggert <eggert@cs.ucla.edu>
Thu, 5 Jan 2006 21:43:44 +0000 (5 21:43 +0000)
treeb82160ca5d83e76a00b9989394ab2731ea10c1a9
parenta3195854a5c0d7440dd5638bd933c1e95ba208c8
Fix Posix-conformance bugs re use of { command in sed scripts,
and improve the sed-related documentation a bit.
* doc/autoconf.texi (Installation Directory Variables): Use
our own style advice re 's,a,b,' versus 's|a|b|'.  Use "Sed"
rather than "sed" when talking about Sed in general.
(Particular Programs): Likewise.
(Coding Style): y is like s with respect to / and ,.
(Limitations of Usual Tools): Document the weird restrictions
that Posix has about { }.  Use better quoting.
* lib/autoconf/status.m4 (_AC_OUTPUT_FILES_PREPARE, _AC_OUTPUT_HEADER):
Rewrite to conform to Posix rules about { } in sed scripts.
* lib/m4sugar/m4sh.m4 (AS_DIRNAME_SED, AS_BASENAME_SED): Likewise.
* tests/foreign.at (Libtool): Likewise.
* tests/semantics.at (AC_CHECK_PROG & AC_CHECK_PROGS):
Use our own style advice re 's,a,b,' versus 's|a|b|'.
ChangeLog
doc/autoconf.texi
lib/autoconf/status.m4
lib/m4sugar/m4sh.m4
tests/foreign.at
tests/semantics.at