Re: PATCH: Re: Odd trap return status

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

On Wed, 29 May 2002, Peter Stephenson wrote:

> We save and restore a whole load of status for all traps, which isn't
> necessary if they are fake traps which are never caused by signals.
> This is a minimal patch for that.

Hrm.  This seems wrong to me.  TRAPDEBUG definitely MUST NOT affect the
return code, etc., of the surrounding function.

It would seem to me that even TRAPEXIT should not change values such as
list_pipe_job and badcshglob.

> However, are execsave() and execrestore() necessary now we queue signals
> until some suitable point?

I think they still are needed, though maybe not in as many cases and
perhaps not for all the globals that currently are saved.