From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12674 invoked by alias); 15 Apr 2015 15:14:08 -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: 34893 Received: (qmail 25407 invoked from network); 15 Apr 2015 15:13:56 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=BUneZdCTO3+BvX5BRDGepVHJDr7XTYjsO28XTXCKf2U=; b=I2KEDsKz3j5VerqG84ij8WiLjhSo2ORzJgonUImE0DOifdLXy5LtvMn3irWUxb3tZ8 osvWmir/1smJSmOAQQ8nbfxp9MEl8Tb8CEGq/uGwlLg/UvRskzAMRZsQzQ23jtWnmNUt CJUdmDrCleiOiaRRcrZYgG1jeo4xyCZlF/ZysqLaL4dAcPlMheang9yEOYPY1Q+1tb2z rbtZnuwGAbnhYXuuiR1bnGSu9UYBazKLie2esxGWJG99pj6jXNRkNKLXNPCsxqysL9Ba qZSfUhQpc6gA1JAIwf7IyLWTEPojELxsNcwMAl5qzCZEnBEP/yvU2VKabWlXT54DmMWb qGdg== X-Gm-Message-State: ALoCoQnGdIwUPsSzuU4qarDNtRL+IEew1ZpnIH5ptCC7ayV9bI2AaemSjrO+YzFZ/jYNuCiPsvZf X-Received: by 10.60.45.244 with SMTP id q20mr13943840oem.35.1429110831861; Wed, 15 Apr 2015 08:13:51 -0700 (PDT) From: Bart Schaefer Message-Id: <150415081348.ZM26219@torch.brasslantern.com> Date: Wed, 15 Apr 2015 08:13:48 -0700 In-Reply-To: <20150415100324.296ffa3e@pwslap01u.europe.root.pri> Comments: In reply to Peter Stephenson "Re: broken parsing with $((`:`))" (Apr 15, 10:03am) References: <20150415030531.GA8187@vapier> <20150415100324.296ffa3e@pwslap01u.europe.root.pri> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: broken parsing with $((`:`)) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Apr 15, 10:03am, Peter Stephenson wrote: } } Yes, indeed --- there's a funny internal special case for empty strings } that I never quite get my head around. } } - if (!*s) { } + if (!*s || *s == Nularg) { I wonder if (a) there are other overlooked cases like this and (b) if it would be useful to have a #define macro for (c == '\0' || c == Nularg). A quick grep doesn't find existing cases of that test other than this new one, but of course if the Nularg part were forgotten, it wouldn't. I suspect it just isn't that common because Nularg goes away after the parsing pass. } (Please, God, make the problems with command and math substitution } parsing stop now.) Indeed ... at what point should we consider 5.0.8 to get all these little edge-case fixes out into the field?