Stas Bekman wrote:
>
> Of course, I thought that's what you want, so you can do a binary and
> and figure out what has failed.
Okey, how do a bitwise AND in the shell in a portable way?
> OK, but harness may fail for different reasons, why do you want to
> scratch the status code of the failure? Currently you don't care, but
> someone may want to know the failure status and program the launching
> program to act accordingly.
Fine. That's an excellent point. Now, if only I can figure out
a better way to test this than
STATUS=$?
if perl -e "exit (($STATUS & 0xc8) == 0xc8);" ; then
harness_failed
elif test "x$STATUS" != "x0" ; then
test_failed
fi
:-)
--
#ken P-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http://Apache-Server.Com/
"Millenium hand and shrimp!"
