zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: Re: Odd trap return status
Date: Wed, 29 May 2002 18:50:26 +0100	[thread overview]
Message-ID: <15927.1022694626@csr.com> (raw)
In-Reply-To: "Bart Schaefer"'s message of "Wed, 29 May 2002 10:27:29 PDT." <Pine.LNX.4.44.0205291021500.2351-100000@ns1.sodaware.com>

Bart Schaefer wrote:
> 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.

I think you may be missing the point a bit, unless I am...

  trap 'return 1' DEBUG

would already cause a return from the enclosing function, only the
return status would get lost.  I haven't changed the command flow at
all, only the effect on status variables.  So it seems to me illogical
to insist that the return value be lost.  (However, you can argue that
applies to traps from real signals, too.)

The other stuff --- list_pipe_job, etc. --- should be maintained
consistently anyway.  The point about saving it was not because the
function shouldn't affect the surroundings --- if it was, we would need
to do it in a whole load of other cases such as precmd --- but because
the signal could happen at a point where the shell was already in the
middle of executing something else, and this could cause an inconsistent
state which we needed to recover from.

I think.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 392070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************


  reply	other threads:[~2002-05-29 17:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 15:19 Peter Stephenson
2002-05-29 14:18 ` PATCH: " Peter Stephenson
2002-05-29 17:27   ` Bart Schaefer
2002-05-29 17:50     ` Peter Stephenson [this message]
2002-05-29 18:00       ` Bart Schaefer
2002-05-29 18:34         ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15927.1022694626@csr.com \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).