Skip to content
This repository was archived by the owner on Nov 20, 2024. It is now read-only.

Commit bb70624

Browse files
committed
Imported from ../bash-2.04.tar.gz.
1 parent b72432f commit bb70624

File tree

387 files changed

+31142
-11954
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

387 files changed

+31142
-11954
lines changed

CHANGES

+606
Large diffs are not rendered by default.

COMPAT

+8-1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
This document details the incompatibilites between this version of bash,
2-
bash-2.03, and the previous widely-available version, bash-1.14 (which
2+
bash-2.04, and the previous widely-available version, bash-1.14 (which
33
is still the `standard' version for many Linux distributions). These
44
were discovered by users of bash-2.x, so this list is not comprehensive.
55

@@ -124,3 +124,10 @@ were discovered by users of bash-2.x, so this list is not comprehensive.
124124
when in POSIX mode. The bash-1.14 behavior may be obtained with
125125

126126
<>filename 1>&0
127+
128+
12. The `alias' builtin now checks for invalid options and takes a `-p'
129+
option to display output in POSIX mode. If you have old aliases beginning
130+
with `-' or `+', you will have to add the `--' to the alias command
131+
that declares them:
132+
133+
alias -x='chmod a-x' --> alias -- -x='chmod a-x'

CWRU/POSIX.NOTES

+22-19
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ Bash POSIX Mode
33

44
Starting Bash with the `--posix' command-line option or executing `set
55
-o posix' while Bash is running will cause Bash to conform more closely
6-
to the POSIX.2 standard by changing the behavior to match that
7-
specified by POSIX.2 in areas where the Bash default differs.
6+
to the POSIX 1003.2 standard by changing the behavior to match that
7+
specified by POSIX in areas where the Bash default differs.
88

99
The following list is what's changed when `POSIX mode' is in effect:
1010

@@ -19,16 +19,16 @@ The following list is what's changed when `POSIX mode' is in effect:
1919

2020
4. Reserved words may not be aliased.
2121

22-
5. The POSIX.2 `PS1' and `PS2' expansions of `!' to the history
22+
5. The POSIX 1003.2 `PS1' and `PS2' expansions of `!' to the history
2323
number and `!!' to `!' are enabled, and parameter expansion is
2424
performed on the values of `PS1' and `PS2' regardless of the
2525
setting of the `promptvars' option.
2626

2727
6. Interactive comments are enabled by default. (Bash has them on by
2828
default anyway.)
2929

30-
7. The POSIX.2 startup files are executed (`$ENV') rather than the
31-
normal Bash files.
30+
7. The POSIX 1003.2 startup files are executed (`$ENV') rather than
31+
the normal Bash files.
3232

3333
8. Tilde expansion is only performed on assignments preceding a
3434
command name, rather than on all assignment statements on the line.
@@ -48,49 +48,52 @@ The following list is what's changed when `POSIX mode' is in effect:
4848
13. Redirection operators do not perform filename expansion on the word
4949
in the redirection unless the shell is interactive.
5050

51-
14. Function names must be valid shell `name's. That is, they may not
51+
14. Redirection operators do not perform word splitting on the word in
52+
the redirection.
53+
54+
15. Function names must be valid shell `name's. That is, they may not
5255
contain characters other than letters, digits, and underscores, and
5356
may not start with a digit. Declaring a function with an invalid
5457
name causes a fatal syntax error in non-interactive shells.
5558

56-
15. POSIX.2 `special' builtins are found before shell functions during
57-
command lookup.
59+
16. POSIX 1003.2 `special' builtins are found before shell functions
60+
during command lookup.
5861

59-
16. If a POSIX.2 special builtin returns an error status, a
62+
17. If a POSIX 1003.2 special builtin returns an error status, a
6063
non-interactive shell exits. The fatal errors are those listed in
6164
the POSIX.2 standard, and include things like passing incorrect
6265
options, redirection errors, variable assignment errors for
6366
assignments preceding the command name, and so on.
6467

65-
17. If the `cd' builtin finds a directory to change to using
68+
18. If the `cd' builtin finds a directory to change to using
6669
`$CDPATH', the value it assigns to the `PWD' variable does not
6770
contain any symbolic links, as if `cd -P' had been executed.
6871

69-
18. If `$CDPATH' is set, the `cd' builtin will not implicitly append
72+
19. If `$CDPATH' is set, the `cd' builtin will not implicitly append
7073
the current directory to it. This means that `cd' will fail if no
7174
valid directory name can be constructed from any of the entries in
7275
`$CDPATH', even if the a directory with the same name as the name
7376
given as an argument to `cd' exists in the current directory.
7477

75-
19. A non-interactive shell exits with an error status if a variable
78+
20. A non-interactive shell exits with an error status if a variable
7679
assignment error occurs when no command name follows the assignment
7780
statements. A variable assignment error occurs, for example, when
7881
trying to assign a value to a readonly variable.
7982

80-
20. A non-interactive shell exits with an error status if the iteration
83+
21. A non-interactive shell exits with an error status if the iteration
8184
variable in a `for' statement or the selection variable in a
8285
`select' statement is a readonly variable.
8386

84-
21. Process substitution is not available.
87+
22. Process substitution is not available.
8588

86-
22. Assignment statements preceding POSIX.2 special builtins persist
87-
in the shell environment after the builtin completes.
89+
23. Assignment statements preceding POSIX 1003.2 special builtins
90+
persist in the shell environment after the builtin completes.
8891

89-
23. The `export' and `readonly' builtin commands display their output
90-
in the format required by POSIX.2.
92+
24. The `export' and `readonly' builtin commands display their output
93+
in the format required by POSIX 1003.2.
9194

9295

93-
There is other POSIX.2 behavior that Bash does not implement.
96+
There is other POSIX 1003.2 behavior that Bash does not implement.
9497
Specifically:
9598

9699
1. Assignment statements affect the execution environment of all

0 commit comments

Comments
 (0)