From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26370 invoked by alias); 25 Sep 2015 09:15:56 -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: 36628 Received: (qmail 4117 invoked from network); 25 Sep 2015 09:15:55 -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 X-AuditID: cbfec7f4-f79c56d0000012ee-5c-560510c6e68b Date: Fri, 25 Sep 2015 10:15:40 +0100 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: Proof of concept: "static" parameter scope Message-id: <20150925101540.5d2ded9c@pwslap01u.europe.root.pri> In-reply-to: <150924192305.ZM2680@torch.brasslantern.com> References: <150924192305.ZM2680@torch.brasslantern.com> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMLMWRmVeSWpSXmKPExsVy+t/xa7rHBFjDDHpvcFkcbH7I5MDoserg B6YAxigum5TUnMyy1CJ9uwSujKV/XQuuslccePCftYFxNlsXIyeHhICJxMpza5khbDGJC/fW A8W5OIQEljJKvNmwjBHCmcEkcfLlPChnG6PE6i2HmUBaWARUJe4sXMUOYrMJGEpM3TSbEcQW ERCXOLv2PAuILSxgLvFo8RxWEJtXwF7ie8MrsHpOAUuJuetWga0WErCQuD3pG9hMfgF9iat/ PzFBnGQvMfPKGUaIXkGJH5Pvgc1kFtCS2LytiRXClpfYvOYt1Bx1iRt3d7NPYBSahaRlFpKW WUhaFjAyr2IUTS1NLihOSs811CtOzC0uzUvXS87P3cQICdovOxgXH7M6xCjAwajEw6vQyhIm xJpYVlyZe4hRgoNZSYS36g9QiDclsbIqtSg/vqg0J7X4EKM0B4uSOO/cXe9DhATSE0tSs1NT C1KLYLJMHJxSDYwTXgbFN1isTTuyd3l0UqZ/mlb1wTmmtm5CV/wLQ15NT+gQ939t126v/Nmo 5aGzyqKMCcKKLzwfFbivmLD0opRV5I5P/4P3NerXtz/gcbcOnPOGP/OH68Iz6/9cd/bTEf82 ve2TmO7DZ1+e8rf8OLal9C73hCO93UtSt+XeKbKp7DtXaFz9fZESS3FGoqEWc1FxIgAbJb2E VgIAAA== On Thu, 24 Sep 2015 19:23:05 -0700 Bart Schaefer wrote: > Modules can't declare keywords, so this isn't able to support the new > array assignment syntax used by "local" et al. However, the entry point > is coded to match that call signature. I think the biggest issue with fixing this is it's going to change the "features" interface to modules as we'll have to add a feature type that defines a typeset-style interface (and a corresponding reserved word, but I think we can tie the two together). But fiddling with the system to get a module added is already tough enough that that may not cause much real practical trouble. Typically, I think modules would then do what "typeset" effectively does (hard-wired rather than via features) and declare both a builtin and an enhanced version as separate features, and we should probably mention this in the development guidelines. Not sure what to do about printparamnode(). pws