From: David MacKenzie Date: Tue, 13 Sep 1994 05:21:44 +0000 (+0000) Subject: mention negated character classes X-Git-Tag: fsf-origin~452 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=be9e449b56175d6339e095919816b86f016b5977;p=thirdparty%2Fautoconf.git mention negated character classes --- diff --git a/autoconf.texi b/autoconf.texi index e030be005..f431a6d9d 100644 --- a/autoconf.texi +++ b/autoconf.texi @@ -2692,13 +2692,14 @@ with a different return type (such as @code{char}). @section Portable Shell Programming When writing your own checks, there are some shell script programming -techniques you should avoid in order to make your code portable. -The Bourne shell and upward-compatible shells like Bash and the Korn -shell have evolved over the years, but to prevent trouble, do not take +techniques you should avoid in order to make your code portable. The +Bourne shell and upward-compatible shells like Bash and the Korn shell +have evolved over the years, but to prevent trouble, do not take advantage of features that were added after UNIX version 7, circa 1977. -You should not use shell functions, aliases, or other features that are -not found in all Bourne-compatible shells; restrict yourself to the -lowest common denominator. Even @code{unset} is not supported by all shells! +You should not use shell functions, aliases, negated character classes, +or other features that are not found in all Bourne-compatible shells; +restrict yourself to the lowest common denominator. Even @code{unset} +is not supported by all shells! The set of external programs you should run in a @code{configure} script is fairly small. @xref{Utilities in Makefiles, , Utilities in diff --git a/doc/autoconf.texi b/doc/autoconf.texi index e030be005..f431a6d9d 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -2692,13 +2692,14 @@ with a different return type (such as @code{char}). @section Portable Shell Programming When writing your own checks, there are some shell script programming -techniques you should avoid in order to make your code portable. -The Bourne shell and upward-compatible shells like Bash and the Korn -shell have evolved over the years, but to prevent trouble, do not take +techniques you should avoid in order to make your code portable. The +Bourne shell and upward-compatible shells like Bash and the Korn shell +have evolved over the years, but to prevent trouble, do not take advantage of features that were added after UNIX version 7, circa 1977. -You should not use shell functions, aliases, or other features that are -not found in all Bourne-compatible shells; restrict yourself to the -lowest common denominator. Even @code{unset} is not supported by all shells! +You should not use shell functions, aliases, negated character classes, +or other features that are not found in all Bourne-compatible shells; +restrict yourself to the lowest common denominator. Even @code{unset} +is not supported by all shells! The set of external programs you should run in a @code{configure} script is fairly small. @xref{Utilities in Makefiles, , Utilities in