From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13449 invoked by alias); 4 Nov 2015 18:31:41 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 20897 Received: (qmail 8510 invoked from network); 4 Nov 2015 18:31:41 -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-Authority-Analysis: v=2.1 cv=X+5rdgje c=1 sm=1 tr=0 a=NKvc7L9z7/b0bXwZ1ZmuGA==:117 a=NKvc7L9z7/b0bXwZ1ZmuGA==:17 a=N659UExz7-8A:10 a=EME7wGNd6Zvh9ESiz2UA:9 a=pILNOxqGKmIA:10 Message-id: <563A4F06.40807@eastlink.ca> Date: Wed, 04 Nov 2015 10:31:34 -0800 From: Ray Andrews User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-version: 1.0 To: zsh-users@zsh.org Subject: Re: easy calling of associative array? References: <56369C7B.2030604@eastlink.ca> <1237641446422150@web6m.yandex.ru> <5636B333.8060300@eastlink.ca> <151101190842.ZM16752@torch.brasslantern.com> <5636D99F.2030807@eastlink.ca> <151101225100.ZM16882@torch.brasslantern.com> <563784B5.3040901@eastlink.ca> <151102082808.ZM17640@torch.brasslantern.com> <5637AC27.8010007@eastlink.ca> <151102130518.ZM17830@torch.brasslantern.com> <5637EB66.9050301@eastlink.ca> <151103075730.ZM18820@torch.brasslantern.com> <563A1ACF.4020902@eastlink.ca> <151104083933.ZM20328@torch.brasslantern.com> In-reply-to: <151104083933.ZM20328@torch.brasslantern.com> Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 7bit On 11/04/2015 08:39 AM, Bart Schaefer wrote: > On Nov 4, 6:48am, Ray Andrews wrote: > } > } Historian that I am, I expect that if the writers of the first shells > } realized how far their work would evolve, they'd have introduced > } rigorous C-ish scoping and typing at the getgo, since largeish > } projects sure could use it. > > Historically no one would have written that sort of project in shell; > that's what C was for. Even functions are a bolt-on to the original > shells; there was no scoping to consider at the time. Yeah, that's about what I was saying. Interesting how things evolve past what their body plans are really designed for (fruit bats, rhinoceros beetles, London street plan), and how those body plans adapt to cope with it. I do now quite understand that there is a limit to how big a zsh project should get to be. Still you know, will all these fantastic little build in manipulations that zsh can perform, one might long for something that combines that power with the robustness of C type checking and so on. Dunno, maybe that's Python or Ruby--haven't looked at them yet. But the experiments I'm doing now are cool, I've pretty much got data arrays being passed by what more or less amounts to a 'pointer' to look at it tho of course it ain't really a pointer, so it satisfies. >