From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: break/continue vs. try-always
Date: Sun, 8 Jun 2014 21:29:50 +0100 [thread overview]
Message-ID: <20140608212950.7384ba2b@pws-pc.ntlworld.com> (raw)
In-Reply-To: <20140608204358.4ec607b8@pws-pc.ntlworld.com>
On Sun, 8 Jun 2014 20:43:58 +0100
Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> If you like the idea of function scope as a sandbox, it seems me that a
> neater way to handle this would be to add an option to force break and
> continue to respect function scope. Then no new syntax is required.
> Provide you define that the new option (call it localloops for now) is
> applied in the outer function on return from the inner, you can do
> everything with
>
>
> setopt localoptions localloops
> () {
> # call user code
> }
> # localloops is restored on return here and used to cancel breaks /
> # contflag before resuming user code at this point.
A further thought is we could even flag an error if there was a break or
continue pending at this point, since evidently the user tried to do
something they shouldn't. Then we could get the continue-outside-a-loop
test to work, thought it wouldn't quite be testing the code it was meant
to test.
pws
next prev parent reply other threads:[~2014-06-08 20:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 2:12 Oddball output from zerrmsg() Bart Schaefer
2014-06-05 5:37 ` [PATCH] " Bart Schaefer
2014-06-05 15:53 ` break/continue vs. try-always Bart Schaefer
2014-06-06 20:58 ` Peter Stephenson
2014-06-06 21:08 ` Bart Schaefer
2014-06-06 21:45 ` Peter Stephenson
2014-06-07 6:22 ` Bart Schaefer
2014-06-08 17:54 ` Peter Stephenson
2014-06-08 18:41 ` Bart Schaefer
2014-06-08 19:43 ` Peter Stephenson
2014-06-08 20:29 ` Peter Stephenson [this message]
2014-06-08 21:01 ` Bart Schaefer
2014-06-08 21:50 ` Peter Stephenson
2014-06-09 2:11 ` Bart Schaefer
2014-06-12 19:35 ` Peter Stephenson
2014-06-13 6:57 ` Bart Schaefer
2014-06-13 9:55 ` 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=20140608212950.7384ba2b@pws-pc.ntlworld.com \
--to=p.w.stephenson@ntlworld.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).