zsh-workers
 help / color / mirror / code / Atom feed
From: Philippe Altherr <philippe.altherr@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: New problem with ERR_RETURN ?
Date: Wed, 7 Dec 2022 17:41:53 +0100	[thread overview]
Message-ID: <CAGdYchvWXmsLZ_ohhdZsqy=1tTR2R25uHKi=vuqNu9uMA7MP=Q@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7Y-rW_Lid-2F1JK+UC+2tG2F7yPfcguC86-sWR0MpG+-g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

I don't think there is a problem. At least not a new problem because Zsh
5.8 and Zsh dev behave the same way.

Note that if you replace the body of "f" with just "false" you get the same
results.

Note also that if you run "return; echo $?" nothing is printed.

From that I concluded that the example behaves correctly. The function "f"
returns a non-zero status. Therefore the call to "f" triggers a return,
which at the top-level simply exits the script/returns to the command line
and thus bypasses what comes next.

Philippe


On Wed, Dec 7, 2022 at 5:17 PM Bart Schaefer <schaefer@brasslantern.com>
wrote:

> After zsh-workers 51001, 51071, 51076 (Philippe A.)
>
> This seems wrong:
>
> % setopt errreturn
> % f() {
>     while return 5
>     do
>         echo fail while1
>         break
>     done
> }
> % f ; echo $?
> %
>
> Note that "echo $?" was not executed when it appears in the same
> command line as "f".  I don't believe ERR_RETURN should be having an
> effect there.
>
> Compare:
>
> % f
> % echo $?
> 5
> %
>
>

[-- Attachment #2: Type: text/html, Size: 1602 bytes --]

  parent reply	other threads:[~2022-12-07 16:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07 16:17 Bart Schaefer
2022-12-07 16:37 ` Peter Stephenson
2022-12-07 16:41 ` Philippe Altherr [this message]
2022-12-07 16:53   ` Peter Stephenson
2022-12-07 17:02     ` Bart Schaefer
2022-12-07 17:07       ` Peter Stephenson
2022-12-08  6:05         ` Lawrence Velázquez
2022-12-08  9:24           ` Peter Stephenson
2022-12-07 16:58   ` Bart Schaefer

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='CAGdYchvWXmsLZ_ohhdZsqy=1tTR2R25uHKi=vuqNu9uMA7MP=Q@mail.gmail.com' \
    --to=philippe.altherr@gmail.com \
    --cc=schaefer@brasslantern.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).