[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: incorrect return code on vms...
From: |
Larry Jones |
Subject: |
Re: incorrect return code on vms... |
Date: |
Fri, 1 Dec 2000 13:53:51 -0500 (EST) |
Derek R. Price writes:
>
> Still, where's the harm in returning only EXIT_SUCCESS & EXIT_FAILURE on
> systems that require that and a little more information on systems which
> support it?
There isn't any. I wasn't arguing for or against that change, just
explaining why things are the way they are.
> We're talking about a few lines in configure.in, maybe one
> in acconfig.h, a line in system.h, and a single line in main. I'll do
> the work, or what Donald hasn't done already.
Remember that autoconf only works on Unix-like systems. I don't think
that's a big problem, but if you're going to have multiple exit
statuses, you should probably #define them in such a way that they can
be overridden in a system-dependent way.
> P.S. run.c already seems to non-portably _exit() with bash's 127 when
> it can't exec a program.
Like I said, CVS isn't quite there yet.
-Larry Jones
Even if lives DID hang in the balance, it would depend on whose they were.
-- Calvin
- Re: incorrect return code on vms..., (continued)
Re: incorrect return code on vms..., Noel L Yap, 2000/12/01
Re: incorrect return code on vms..., Larry Jones, 2000/12/01
Re: incorrect return code on vms..., Rex_Jolliff, 2000/12/04
Re: incorrect return code on vms..., Rex_Jolliff, 2000/12/04