From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8483 invoked by alias); 30 Sep 2015 15:06:31 -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: 20669 Received: (qmail 20125 invoked from network); 30 Sep 2015 15:06:29 -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=62AtbbSsrca3scplPJj5lw==:117 a=62AtbbSsrca3scplPJj5lw==:17 a=N659UExz7-8A:10 a=a2Pw0g4eLI6uxHrqYuoA:9 a=pILNOxqGKmIA:10 Message-id: <560BFA70.9010402@eastlink.ca> Date: Wed, 30 Sep 2015 08:06:24 -0700 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: wheels within wheels References: <55FAE223.2080502@eastlink.ca> <150917103419.ZM10067@torch.brasslantern.com> <150918171441.ZM27212@torch.brasslantern.com> <55FD7982.9030505@eastlink.ca> <150919092922.ZM28214@torch.brasslantern.com> <55FDA5D3.9020304@eastlink.ca> <150919142243.ZM23634@torch.brasslantern.com> <55FE04AD.1070304@eastlink.ca> <150919224120.ZM4736@torch.brasslantern.com> <55FF3F7E.4060906@eastlink.ca> <150920211840.ZM31871@torch.brasslantern.com> <5600386E.7060201@eastlink.ca> <150921111746.ZM388@torch.brasslantern.com> <56006401.5060902@eastlink.ca> <150921201943.ZM707@torch.brasslantern.com> <560B1BE7.8020507@eastlink.ca> <150929204047.ZM9646@torch.brasslantern.com> <560B61C5.2080001@eastlink.ca> <150930000505.ZM21759@torch.brasslantern.com> In-reply-to: <150930000505.ZM21759@torch.brasslantern.com> Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 7bit On 09/30/2015 12:05 AM, Bart Schaefer wrote: > On Sep 29, 9:15pm, Ray Andrews wrote: > } > } Each command is past when it's past so that must mean that the address > } of first foo ... is there ... yes of course there is, the thing is in > } memory ... just aborts when second foo comes along. > > No, the outer foo will happily keep executing until it returns, at > which point it is garbage-collected. The old body has merely been > disconnected from the name. That's better. It's not 'abandoned' it just becomes nameless. Else we'd have orphan lines of code and that's not sanitary.