mirror/autoconf
2
0
Fork 0
mirror of git://git.sv.gnu.org/autoconf synced 2025-03-25 14:50:24 +08:00
Code Issues Packages Projects Releases Wiki Activity

mention negated character classes

Browse Source
This commit is contained in:
David MacKenzie 1994-09-13 05:21:44 +00:00
parent 8c3488e0e8
commit be9e449b56
2 changed files with 14 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
autoconf.texi
View File

@ -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

13
doc/autoconf.texi
View File

@ -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