Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: "{ } always { }" construct and return in called functions

X-seq: zsh-workers 35275
From: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
To: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
Subject: Re: "{ } always { }" construct and return in called functions
Date: Sat, 23 May 2015 10:49:06 +0000
Cc: zsh workers <zsh-workers@xxxxxxx>
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=Q8xJ03Flo6U3jnMEaukY+wEmO60=; b=ziwaOV K94wOhUN3hzVA6GaDiGGfGBljyG5maQanSyRvZCZmU5kYia5rBX8KM9tymLZtFS2 JhdzudtwTyENBlJzJTrdYzHxXX3UpmE42kG8rFTe5rbq1V5n7kPCkQIqlqmavJXO JqL0msVPZnKF0sfOGQ2snz9bzKS6WKsE4ugZU=
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=Q8xJ03Flo6U3jnMEaukY+wEmO60=; b=iKP7g sewQQB7AHBUkp/zHGmlhbCW88dCFUdnHea5VxXMP+olklECjgTBRazzKj6DhCkrI bXDDcRebwZZn008u2oVZjj52DnQN2yYLVpZeM1CDJBfe05GdE6oS9QLQacLPzAmA TIOOf4mqsrrR0or0JRuN52SiY/LT49O4dyvh/k=
In-reply-to: <20150522233113.76b13026@ntlworld.com>
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
References: <CAHfspHmUOgLjnEMtLBBoeU31Z2GKu8uD5MYE4jsogMKbf+ag9g@mail.gmail.com> <20150513155915.71f3daaa@pwslap01u.europe.root.pri> <CAHYJk3RBn_U_ZTNXWHeBfAJyibspcx1=gMM2OTmXz2cpsrrY2Q@mail.gmail.com> <20150522233113.76b13026@ntlworld.com>

Peter Stephenson wrote on Fri, May 22, 2015 at 23:31:13 +0100:
> This is the last thing I have to look at; is anyone else expecting
> something to happen?

[ I assume you're asking if there are release blockers. ]

I *think* the compdescribe stuff is fine.  All of the issues discussed
in that thread are either not new or not happening in master.  My main
concern is that 35127#1 might have introduced a bug that hasn't been
noticed yet.  I'm more concerned about that patch than usual since it is
my first patch to comp*.c and I'm not at home in that part of the code, yet.

Cheers,

Daniel

References:
- Re: "{ } always { }" construct and return in called functions
  - From: Mikael Magnusson
- Re: "{ } always { }" construct and return in called functions
  - From: Peter Stephenson

Messages sorted by: Reverse Date, Date, Thread, Author