From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22580 invoked by alias); 25 Jul 2017 05:04:18 -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: 41452 Received: (qmail 14219 invoked from network); 25 Jul 2017 05:04:18 -0000 X-Qmail-Scanner-Diagnostics: from mail-qk0-f175.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.220.175):SA:0(-2.3/5.0):. Processed in 3.484217 secs); 25 Jul 2017 05:04:18 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,RCVD_IN_SORBS_SPAM,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.220.175 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=PcXpEg2goKxs5AvleG5nRc6Jo3jzsp3D2Je1ZYPEIW4=; b=IGmGgUfW+4qkkMyoX3S1DDyQKWuvUa9RKxrmQb3n6jeRnLzDqi6CsyU0ztlnbak6Gn xwXMj/6OApBndSn3TkyniZtLGFK4fs1lsFctow6GnSMSCstJJK7AgsgEz86+s8fMX3UB Cs7jYmmCSB/R2ij9b3IZLH7A2g0kUptaiYeJzYbKkx54R+shYJEG9T3zNczrfc7qBYpb 70fH/GQN1I6iUWGFFpm5WxUqBhn8t3lCSwPTDFH1Y4+vCIUd7T7JxKLgrDlHa61397k5 6LQw3Yo4LTeT1udYWWyLORTFgUNRzPvz5ecK803jRUO95TbgmlbFIMA2giS4K8Qw1EGp Le1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=PcXpEg2goKxs5AvleG5nRc6Jo3jzsp3D2Je1ZYPEIW4=; b=cDZEsVIHVf9y4lhtz6WMKDd/yIMDVQmXv3bXivBgr94WcI18t53xuVKRV+ornKPd3c xczE2xlsxuCbCcj3OG5jMjeHKc9oNB9Nikg0IKkMfZ5fUXEFiMWUz7rEbQDoz5yXZCv2 +I5FpOZcdPLUL8MrFMPkvLHQSDMpUgz0J9QvprAmvHxZeRuAIAqxYBe0vTkQkTl08KWB 5yuFQjuJ5gYqwXahJQ831alG7k5qjPnKR0o3HvkliXWyu+uzaFOqZ2Xo5Akm7MXp/DTg KHu691yQnOEfjCkmcn23hfDeUT1qw03VZ7uKzc498spj8+F7yJNyHW/fIYVeLz+SVyrK V0fg== X-Gm-Message-State: AIVw113Z1T1AJ/8Y/xQIHPrH060usZd8ZLLuihdXSrHD7j/EtAbBrS0q C5++8qC13FkZmyz+a0CZVXLXgbexsOR1 X-Received: by 10.55.7.139 with SMTP id 133mr22134270qkh.165.1500959048493; Mon, 24 Jul 2017 22:04:08 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Bart Schaefer Date: Mon, 24 Jul 2017 22:04:07 -0700 Message-ID: Subject: Re: Can ZWC be optimized, for lesser depths of recursive exec* calls? To: "zsh-workers@zsh.org" Content-Type: text/plain; charset="UTF-8" On Mon, Jul 24, 2017 at 6:26 PM, Sebastian Gniazdowski wrote: > > It's just that I suspect "recurse and forget" tactics in exec.c. I don't know what you mean by this.