On 1/11/12 3:03 PM, Linda Walsh wrote:
> Like... compat40 mentions it changes behavior, about interrupting a command
> list, yet try to find out what that behavior is, or what compat40 would
> change it 'to'?
Thanks, I added that to the description. It means that bash versions
later than 4.0 interrupt a list when one of the commands in the list
terminates due to SIGINT and job control is in effect; previous versions
just continued on.
>
> Or how about, does compat 31 imply compat32 and compat40? If not, does that
> really mean compat31 is really 'compat31', or just "use <feature> 3.1" to
> specify that a specific feature be used in it's 3.1 version vs. a newer
> version.
There is only a single shell compatibility level; the last variable
set wins. The compatibility level variables are mutually exclusive.
The descriptions of each option are self-contained. That's why the
descriptions for compat32 and compat40 include the same text concerning
using strcoll for < and > comparisons (and why the description for
compat31 should include it as well).
The COMPAT file in the bash distribution has a much more extensive
description of incompatibilities between versions.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
