Re: Is there really any interest in a patch to allow cvs 1.11.6

[Derek Robert Price]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Larry Jones wrote:

|Paul Edwards writes:
|
|>and then the call to exit() will convert 1 or 2 into EXIT_FAILURE.
|
|
|So it will.  In that case, the test suite *is* wrong -- the
|dotest_status function is not needed and all of the calls to
|it should just use dotest_fail instead.


Is there a good reason, outside of the C89 spec only guaranteeing
EXIT_SUCCESS & EXIT_FAILURE, for:

~    exit (err ? EXIT_FAILURE : 0);

?

Rather, if I wrote a configure test that tested whether exit(2) returned
2 or some other value and used it to switch the above for `exit(err)',
would anyone raise objections?  It's possible that we could even skip
the above construction altogether.  Granted, C89 specifies:

~    7.10.4.3 The exit function

~    If the value of STATUS is zero or EXIT_SUCCESS, an
implementation-defined form of the status <i>successful termination</i>
is returned.  If the value of STATUS is EXIT_FAILURE, an
implementation-defined form of the status <i>unsuccessful
termination</i> is returned.  Otherwise the status returned is
implementation-defined.

but does anyone know any hosts which, in practice, return some value
other than `unsuccessful termination' or the actual STATUS when STATUS
is a number in the range 2 through 255?

A similar configure test could quite easily tell sanity.sh's
dotest_status function that any non-zero return value it is told to
expect will actually be $EXIT_FAILURE on offending systems.

Derek

- --
~                *8^)

Email: derek@ximbiot.com

Get CVS support at <http://ximbiot.com>!
- --
72. Enter any 11-digit prime number to continue...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQE/hBwALD1OTBfyMaQRArIGAKC3ykBilBoZ1zcWBgltsnAQce73MgCffvbr
Q7B8G7I8GeJwLhdPke7tZYI=
=zFH0
-----END PGP SIGNATURE-----