Skip to content

Commit

Permalink
Imported from ../bash-2.04.tar.gz.
Browse files Browse the repository at this point in the history
  • Loading branch information
jaalto committed Sep 12, 2009
1 parent b72432f commit bb70624
Show file tree
Hide file tree
Showing 387 changed files with 31,142 additions and 11,954 deletions.
606 changes: 606 additions & 0 deletions CHANGES

Large diffs are not rendered by default.

9 changes: 8 additions & 1 deletion COMPAT
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
This document details the incompatibilites between this version of bash,
bash-2.03, and the previous widely-available version, bash-1.14 (which
bash-2.04, and the previous widely-available version, bash-1.14 (which
is still the `standard' version for many Linux distributions). These
were discovered by users of bash-2.x, so this list is not comprehensive.

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

<>filename 1>&0

12. The `alias' builtin now checks for invalid options and takes a `-p'
option to display output in POSIX mode. If you have old aliases beginning
with `-' or `+', you will have to add the `--' to the alias command
that declares them:

alias -x='chmod a-x' --> alias -- -x='chmod a-x'
41 changes: 22 additions & 19 deletions CWRU/POSIX.NOTES
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,8 @@ Bash POSIX Mode

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

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

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

4. Reserved words may not be aliased.

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

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

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

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

14. Function names must be valid shell `name's. That is, they may not
14. Redirection operators do not perform word splitting on the word in
the redirection.

15. Function names must be valid shell `name's. That is, they may not
contain characters other than letters, digits, and underscores, and
may not start with a digit. Declaring a function with an invalid
name causes a fatal syntax error in non-interactive shells.

15. POSIX.2 `special' builtins are found before shell functions during
command lookup.
16. POSIX 1003.2 `special' builtins are found before shell functions
during command lookup.

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

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

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

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

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

21. Process substitution is not available.
22. Process substitution is not available.

22. Assignment statements preceding POSIX.2 special builtins persist
in the shell environment after the builtin completes.
23. Assignment statements preceding POSIX 1003.2 special builtins
persist in the shell environment after the builtin completes.

23. The `export' and `readonly' builtin commands display their output
in the format required by POSIX.2.
24. The `export' and `readonly' builtin commands display their output
in the format required by POSIX 1003.2.


There is other POSIX.2 behavior that Bash does not implement.
There is other POSIX 1003.2 behavior that Bash does not implement.
Specifically:

1. Assignment statements affect the execution environment of all
Expand Down
Loading

0 comments on commit bb70624

Please sign in to comment.