Non POSIX.2 compliance in sh and ksh

[tlaronde%polynum.com@localhost]

Hello,

If I read correctly SUSv4, for the sh(1) unset builtin:

	Unsetting a variable or function that was not previously set shall
	not be considered an error and does not cause the shell to abort.

But if one unset a variable not set, the return status is 1 aborting
the script if -e is set.

I'm on NetBSD 6.1.5_PATCH amd64.

This happens with /bin/ksh and /bin/sh.

Best regards,
-- 
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                     http://www.kergis.com/
                       http://www.sbfa.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C