zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Cc: "Eduardo A. Bustamante Lopez" <dualbus@gmail.com>
Subject: Re: Zsh does not follow POSIX when return is called during the action of a trap
Date: Wed, 12 Mar 2014 17:03:09 +0000	[thread overview]
Message-ID: <20140312170309.48ea7444@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <140312095210.ZM13090@torch.brasslantern.com>

On Wed, 12 Mar 2014 09:52:10 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Mar 12,  8:36am, Eduardo A. Bustamante Lopez wrote:
> }
> } Hi! I first reported this bug to bug-bash, but since it also applies
> } to zsh, I wanted you to know about it.
> 
> Have you tried this with the POSIX_TRAPS option set?
> 
> Zsh does not in general conform to POSIX at all unless you run it with
> the appropriate compatibility settings.

I was going to mention that.  I think it still needs some work --- which
I know how to do in this case.  N.B. you can test this with the line

[ x$ZSH_VERSION != x ] && emulate sh

at the top of the "code" variable.

However, I'm trying to work out what happens with the case

|  trap '(exit BEFORE-RETURN); return EXPLICIT-RETURN-VALUE' SIGNAL
|
|  fn() {
|    (exit BEFORE-ACTION); -block here waiting for signal-
|  }

Should this exit with EXPLICIT-RETURN_VALUE or BEFORE-ACTION?  The
latter is easier to implement but my guess (without ploughing through
the standard) is EXPLICIT-RETURN-VALUE is right here.

pws


  reply	other threads:[~2014-03-12 17:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 15:36 Eduardo A. Bustamante López
2014-03-12 16:52 ` Bart Schaefer
2014-03-12 17:03   ` Peter Stephenson [this message]
2014-03-12 17:47     ` Eduardo A. Bustamante López
2014-03-12 17:49     ` Chet Ramey
2014-03-12 18:23       ` 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=20140312170309.48ea7444@pwslap01u.europe.root.pri \
    --to=p.stephenson@samsung.com \
    --cc=dualbus@gmail.com \
    --cc=zsh-workers@zsh.org \
    /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).