Re: bash 3.1 compile problems under AIX 4.3.3
[EMAIL PROTECTED] wrote: > Configuration Information [Automatically generated, do not change]: > Machine: powerpc > OS: aix4.3.3.0 > Compiler: cc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='powerpc' > -DCONF_OSTYPE='aix4.3.3.0' -DCONF_MACHTYPE='powerpc-ibm-aix4.3.3.0' > -DCONF_VENDOR='ibm' -DLOCALEDIR='/usr/local/share/locale' -DPACKAGE='bash' > -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -I/usr/local/include > -O -qmaxmem=16384 > uname output: AIX ganymede 3 4 43224C00 > Machine Type: powerpc-ibm-aix4.3.3.0 > > Bash Version: 3.1 > Patch Level: 0 > Release Status: release > > Description: > Bash 3.1 does not build out of the box under AIX 4.3.3 with the > native IBM compiler. Does it compile on that version of AIX using gcc? -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live Strong. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Two problems: one in documentation, one philosophical
The first bug is in the bash(1) man page. In the SHELL GRAMMAR ->
Compound Commands -> [[ expression ]] section: "The return value is
0 if the string matches or does not match the pattern, respectively,
and 1 otherwise." This sentence is unclear. It is likely that
"respectively" maps "matches" and "does not match" to the operators ==
and !=, repectively. This should be better expressed in the man page.
The second bug is that {x..y} only makes sense if both x and y are
{numbers,lower-case letters,upper-case letters}. {a..A} should be
invalid and resolve to {a..A}, but instead it sequences backwards: "a
_ ^ ] [ Z Y ... A". This is allowed, I am supposing, by a
simplistic typing mechanism, in which there are just two types:
numbers and letters. However this is too simplistic and should be
changed.
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
