From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15024 invoked by alias); 30 Dec 2015 14:33:07 -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: 37452 Received: (qmail 4626 invoked from network); 30 Dec 2015 14:33:06 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 From: Frank Terbeck To: zsh-workers@zsh.org Subject: More warn_create_global warnings User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) Date: Wed, 30 Dec 2015 15:20:37 +0100 Message-ID: <87mvss6mru.fsf@ft.bewatermyfriend.org> MIME-Version: 1.0 Content-Type: text/plain X-Df-Sender: NDMwNDQ0 Hey workers! With the new warn_create_global behaviour, here is another warning that seems bogus: zsh% foo() { setopt warncreateglobal extendedglob; local f=bar; : ${f:#(#b)b(*)}; } zsh% foo foo: array parameter match created globally in function foo foo: array parameter mbegin created globally in function foo foo: array parameter mend created globally in function foo Do I have to mark those local before using back tracking? Or could those maybe be created in local scope unless they already exist? Regards, Frank -- In protocol design, perfection has been reached not when there is nothing left to add, but when there is nothing left to take away. -- RFC 1925