2009-09-10 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
+ Document sed limitation with escaped metacharacters.
+ * doc/autoconf.texi (Limitations of Usual Tools) <sed>: Use `%'
+ rather than `/' as delimiter in an example `s' command.
+ Document inconsistent treatment of escaped metacharacters.
+ * THANKS: Update.
+ Report by Dave Korn, with additional input from Paolo Bonzini
+ and Eric Blake.
+
Document temporary directory `$tmp' for use in config.status.
* doc/autoconf.texi (Configuration Actions): Document `$tmp'.
* NEWS: Update.
Daniele Arena daniele@ripe.net
Dave Adams adams@hpesdwa.fc.hp.com
Dave Erickson retrorandomaccess@hotmail.com
+Dave Korn dave.korn.cygwin@googlemail.com
Dave Love fx@gnu.org
David Byron dbyron@hheld.com
David Carter david@carter.net
@prindex @command{sed}
Patterns should not include the separator (unless escaped), even as part
of a character class. In conformance with Posix, the Cray
-@command{sed} rejects @samp{s/[^/]*$//}: use @samp{s,[^/]*$,,}.
+@command{sed} rejects @samp{s/[^/]*$//}: use @samp{s%[^/]*$%%}.
+Even when escaped, patterns should not include separators that are also
+used as @command{sed} metacharacters. For example, GNU sed 4.0.9 rejects
+@samp{s,x\@{1\,\@},,}, while sed 4.1 strips the backslash before the comma
+before evaluating the basic regular expression.
Avoid empty patterns within parentheses (i.e., @samp{\(\)}). Posix does
not require support for empty patterns, and Unicos 9 @command{sed} rejects