From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15739 invoked by alias); 5 Jun 2014 15:53:24 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 32718 Received: (qmail 12644 invoked from network); 5 Jun 2014 15:53:23 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <140605085319.ZM4272@torch.brasslantern.com> Date: Thu, 05 Jun 2014 08:53:19 -0700 In-reply-to: <140604223723.ZM22960@torch.brasslantern.com> Comments: In reply to Bart Schaefer "[PATCH] Re: Oddball output from zerrmsg()" (Jun 4, 10:37pm) References: <140603191227.ZM28198@torch.brasslantern.com> <140604223723.ZM22960@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: break/continue vs. try-always MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Jun 4, 10:37pm, Bart Schaefer wrote: } Subject: [PATCH] Re: Oddball output from zerrmsg() } } ... the "continue" propagates } up through the dynamic scopes and restarts the "while true;" loop ... } } Not even an "always" block can intercept this, which is probably a bug in } the handling of "always". OK, not a bug, exactly. The always-block is in fact executed, but it has no way to decrement the number of levels of "break" or "continue" that have been set by the try-block. It can *increase* the number of levels, but not stop the break/continue from propagating upward.