From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-35363-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 29320 invoked by alias); 2 Jun 2015 10:33:14 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 35363
Received: (qmail 26980 invoked from network); 2 Jun 2015 10:33:11 -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=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI,
	RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS autolearn=ham
	autolearn_force=no version=3.4.0
X-AuditID: cbfec7f4-f79c56d0000012ee-0f-556d8408be66
Date: Tue, 02 Jun 2015 11:22:55 +0100
From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: zsh 5.0.8 available (preliminary announcement)
Message-id: <20150602112255.79bd4e03@pwslap01u.europe.root.pri>
In-reply-to: <20175.1433239580@thecus.kiddle.eu>
References: <20150531192334.26a88ef9@ntlworld.com>
 <150531171724.ZM29828@torch.brasslantern.com>
 <CAPKC6oJ0fOEeg1--qpufEYQoxTeUnD8KDNSHV5Sfn7J4EtPYCw@mail.gmail.com>
 <20175.1433239580@thecus.kiddle.eu>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFjrMLMWRmVeSWpSXmKPExsVy+t/xa7ocLbmhBi1dahYHmx8yOTB6rDr4
	gSmAMYrLJiU1J7MstUjfLoEr42RjP1PBavaKbUt+sDcw3mXtYuTkkBAwkTi56TEzhC0mceHe
	erYuRi4OIYGljBKfpj1nhHBmMElMmL0TKrOVUWLflhVMIC0sAqoSexuXs4DYbAKGElM3zWYE
	sUUEtCR2nDwJViMsYC2xeFsDWJxXwF6ipeUB0CAODk4BA4m/i+RBwkIC5xklHv72AbH5BfQl
	rv79xARxkb3EzCtnoFoFJX5Mvge2ihlo/OZtTawQtrzE5jVvmSHmqEvcuLubfQKj0CwkLbOQ
	tMxC0rKAkXkVo2hqaXJBcVJ6rqFecWJucWleul5yfu4mRkjQftnBuPiY1SFGAQ5GJR5ehk85
	oUKsiWXFlbmHGCU4mJVEeF/m54YK8aYkVlalFuXHF5XmpBYfYpTmYFES5527632IkEB6Yklq
	dmpqQWoRTJaJg1OqgbH7TWxtyQbWJuanDSrPmk/uPVNYtnC+2cRlsjfrl147+eTPNtkXs3ee
	OrOOVZmxLf6T3a0epj6nDYsfsIr9PT5hu0uIgK/pNt66qOtPGfnW9Z9QUNMLi8s/uGh98au9
	xuH+T7yO767+pO26/sCq55c3X90yv0/nbsPEPQwzL4dMe7hdqGr2KqatSizFGYmGWsxFxYkA
	zRKGrlYCAAA=

On Tue, 2 Jun 2015 12:06:20 +0200
Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
> Is the -o option to test safe to use in configure? It seems existing
> tests use || and && but the precedence of those wouldn't be right.

I think the definitive answer is "probably, who knows?"  configure has
been written to handle some very ancient implementations of test, but
the things it's more likely to fall down on are what happens with
confusing arguments (as zsh still sometimes does or did), which doesn't
apply here.  You might find better guidance in the autoconf
documentation if there's none in the existing code.

The ultra paranoid way to do it is nest the ifs...

if  test1 || test2; then
  if test3 && test4 && test5 ..; then
    stuff
    done_some_stuff=yes
  fi
fi
if test x$done_some_stuff != xyes; then
  alternative stuff
fi

I committed Baptiste's patch, it looks like you might want to back it
off.

pws