Article View: comp.std.c
Article #3948Re: EXIT_FAILURE problem
From: halasz
Date: Thu, 07 Sep 1995 14:16
Date: Thu, 07 Sep 1995 14:16
25 lines
1322 bytes
1322 bytes
In article <42mta4$2ku@solutions.solon.com>, seebs@solutions.solon.com (Peter Seebach) writes:
: I think you've just never read a word of what anyone's said here.
I did, but you answer an argument that I nevver wrote.
The same applys for all the other answer s that I saw.
: Consider:
:
: _lib_startup() {
: exit(main(magic, magic));
: }
:
: exit(int x) {
: if (x == 0) exits("okay");
: else exits("not-so-ok");
: }
:
: Boom. We have adapted to a system where we exit with strings.
: The library can go further, but who cares? We've
: shown that the library can translate. Tell us, most omniscient,
: how this doesn't work.
The error is that the library indeed translated. We hav prevented the
programmer who uzes this system from uzing "exit" for _other_ exit-status
that he knows is to be had on this system.
My concluzion form all this is that if a programmer wants to return
useful exit-status, too bad.
Technical Details
Message-ID:
<42mus7$n9o@caip.rutgers.edu>Path:
arc1-ca.pugleaf.net!caip.rutgers.edu!not-for-mailReferences:
<jbundyDCw7uo.9sz@netcom.com> <danpop.807723059@rscernix> <42mta4$2ku@solutions.solon.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!caip.rutgers.edu!not-for-mail From: halasz@caip.rutgers.edu Newsgroups: comp.std.c Subject: Re: EXIT_FAILURE problem Date: 7 Sep 1995 10:16:39 -0400 Organization: Rutgers University Message-ID: <42mus7$n9o@caip.rutgers.edu> References: <jbundyDCw7uo.9sz@netcom.com> <danpop.807723059@rscernix> <42mta4$2ku@solutions.solon.com> NNTP-Posting-Host: caip.rutgers.edu