commit bash-20120113 snapshot

1 files changed, 23 insertions, 6 deletions

diff --git a/COMPAT b/COMPAT
index 5b63b9c3..0463c103 100644
--- a/COMPAT
+++ b/COMPAT
@@ -2,9 +2,9 @@ Compatibility with previous versions
 ====================================
 
 This document details the incompatibilities between this version of bash,
-bash-4.1, and the previous widely-available versions, bash-2.x (which is
+bash-4.2, and the previous widely-available versions, bash-2.x (which is
 still the `standard' version for a few Linux distributions) and bash-3.x. 
-These were discovered by users of bash-2.x and 3.x, so this list is not
+These were discovered by users of bash-2.x through 4.x, so this list is not
 comprehensive.  Some of these incompatibilities occur between the current
 version and versions 2.0 and above.
 
@@ -334,19 +334,36 @@ version and versions 2.0 and above.
     behavior (ASCII collating and strcmp(3)) by setting one of the
     `compatNN' shopt options, where NN is less than 41.
 
-45. Command substitutions now remove the caller's trap strings when trap is
+45. Bash-4.1 conforms to the current Posix specification for `set -u':
+    expansions of $@ and $* when there are no positional parameters do not
+    cause the shell to exit.
+
+46. Bash-4.1 implements the current Posix specification for `set -e' and
+    exits when any command fails, not just a simple command or pipeline.
+
+47. Command substitutions now remove the caller's trap strings when trap is
     run to set a new trap in the subshell.  Previous to bash-4.2, the old
     trap strings persisted even though the actual signal handlers were reset.
 
-46. When in Posix mode, a single quote is not treated specially in a
+48. When in Posix mode, a single quote is not treated specially in a
     double-quoted ${...} expansion, unless the expansion operator is
     # or % or the new `//', `^', or `,' expansions.  In particular, it
     does not define a new quoting context.  This is from Posix interpretation
     221.
 
-47. Posix mode shells no longer exit if a variable assignment error occurs
+49. Posix mode shells no longer exit if a variable assignment error occurs
     with an assignment preceding a command that is not a special builtin.
 
+50. Bash-4.2 attempts to preserve what the user typed when performing word
+    completion, instead of, for instance, expanding shell variable
+    references to their value.
+
+51. When in Posix mode, bash-4.2 exits if the filename supplied as an argument
+    to `.' is not found and the shell is not interactive.
+
+52. When compiled for strict Posix compatibility, bash-4.3 does not enable
+    history expansion by default, since it results in a non-conforming
+    environment.
 
 Shell Compatibility Level
 =========================
@@ -378,7 +395,7 @@ compat40 set
 
 compat41 set
 	- interrupting a command list such as "a ; b ; c" causes the execution
-	  of the entire list to be aborted (in versions before bash-4.0,
+	  of the entire list to be aborted (in versions before bash-4.1,
 	  interrupting one command in a list caused the next to be executed)
 	- when in posix mode, single quotes in the `word' portion of a
 	  double-quoted parameter expansion define a new quoting context and