Re: unset command violates IEEE Std 1003.1-2001 on some systems

[Chet Ramey]

> Configuration Information [Automatically generated, do not change]:
> Machine: i586
> OS: linux
> Compiler: gcc -I/usr/src/packages/BUILD/bash-2.05b
> Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i586' 
> -DCONF_OSTYPE='linux' -DCONF_MACHTYPE='i586-suse-linux' -DCONF_VENDOR='suse' 
> -DSHELL -DHAVE_CONFIG_H  -I.  -I. -I./include -I./lib  -O2 -march=i586 
> -mcpu=i686 -fmessage-length=0 -D_GNU_SOURCE -Wall -pipe -g
> uname output: Linux merlin 2.4.19-4GB #1 Fri Sep 13 13:19:15 UTC 2002 i686 
> unknown
> Machine Type: i586-suse-linux
> 
> Bash Version: 2.05b
> Patch Level: 0
> Release Status: release
> 
> Description:
> bash unset will not consistently continue when applying
> "unset" to an undefined variable or function.
> 
> IEEE Std 1003.1-2001 requests that unsetting an unset variable or
> function does NOT cause an error condition. See
> http://www.opengroup.org/onlinepubs/007904975/utilities/unset.html
> 
> However, my Solaris bash 2.05.0(1)-release (from sunfreeware.com)
> behaves differently and exits or sets $? to 1 after set +e. The same is
> true for FreeBSD 4.7 and its bash 2.05b.004 from the ports.

This behavior was changed in bash-2.05b.  Your Solaris box is not running
bash-2.05b.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )

Chet Ramey, ITS, CWRU    chet@po.CWRU.Edu    http://cnswww.cns.cwru.edu/~chet/