From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: [9fans] test command is broken
Date: Mon, 28 Aug 2006 13:46:04 +0100 [thread overview]
Message-ID: <86c5f4f271e260e234a1a93f1f9001f3@hamnavoe.com> (raw)
In-Reply-To: <44E692D6.8060108@lanl.gov>
The patch applied to the test(1) command on 12 August was
incorrect, as shown by this example:
term% test 1 -gt 2 -o 3 -lt 4 && echo yes
yes
term% test 1 -lt 2 -o 3 -lt 4 && echo yes
test: unexpected operator/operand: 3
term%
Because the -a and -o operators don't necessarily
evaluate their right-hand argument, it's wrong to assume
that there should be no arguments remaining when the
top-level expresssion evaluation returns.
The result is not just a spurious error message but possibly
an incorrect truth status, so I would suggest that anyone who
has pulled from sources since 12 August should revert to the
previous version of /386/bin/test.
-- Richard
next prev parent reply other threads:[~2006-08-28 12:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 11:40 [9fans] err 2: arena creation time after last write time Rodolfo (kix)
2006-08-18 14:45 ` David Leimbach
2006-08-19 0:28 ` Rodolfo (kix)
2006-08-19 1:53 ` erik quanstrom
2006-08-19 2:46 ` Gorka guardiola
2006-08-19 18:21 ` [9fans] Searching for text outside Acme yard-ape
2006-08-19 18:33 ` Benn Newman
2006-08-19 20:59 ` Micah Stetson
2006-08-19 21:24 ` Benn Newman
2006-08-20 1:03 ` Micah Stetson
2006-08-19 21:45 ` yard-ape
2006-08-19 21:53 ` Francisco J Ballesteros
2006-08-19 21:02 ` Charles Forsyth
2006-08-20 3:29 ` erik quanstrom
2006-08-20 5:07 ` yard-ape
2006-08-19 4:25 ` [9fans] err 2: arena creation time after last write time Ronald G Minnich
2006-08-19 14:59 ` Rodolfo (kix)
2006-08-19 17:21 ` Gorka guardiola
2006-08-28 12:46 ` Richard Miller [this message]
2006-08-18 20:25 ` csant
2006-08-18 20:29 ` John Floren
2006-08-18 20:38 ` csant
2006-08-18 20:41 ` andrey mirtchovski
2006-08-18 20:46 ` John Floren
2006-08-18 20:46 ` csant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86c5f4f271e260e234a1a93f1f9001f3@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).