Re: trap 0 vs. gcc's configure

[Egmont Koblinger]

Hi,

> This was a change made for POSIX compliance.  It works the same as previously
> when not in posix mode:
>
> caleb.INS.CWRU.Edu(2)$ ./bash
> caleb.INS.CWRU.Edu(3)$ echo $BASH_VERSION
> 3.00.0(2)-release
> caleb.INS.CWRU.Edu(3)$ trap 0
> caleb.INS.CWRU.Edu(3)$ echo $?
> 0

Alright, I see. In the mean time, I've recompiled all the ~1000 packages
of the hungarian linux distribution called UHU-Linux. There were only two
packages whose compilation failed due to this change. One of them is mawk,
which isn't maintained since 1996. The other one is gcc 3.3.4, this is
actively maintained and hopefully will be fixed within days, if not
already fixed in the 3.4.x branch.

So IMHO there's nothing wrong with this posix-compilance change, I don't
think this will cause too many runtime bugs either, but I recommend that
the manpage and 'help trap' should clearly state this fact and hence help
people writing posix-compilant scripts.


thanks,

Egmont