Article View: comp.std.c
Article #3921Re: EXIT_FAILURE problem
From: halasz
Date: Mon, 04 Sep 1995 22:40
Date: Mon, 04 Sep 1995 22:40
6 lines
755 bytes
755 bytes
In article <42eeoo$foo@goanna.cs.rmit.edu.au>, ok@goanna.cs.rmit.edu.au (Richard A. O'Keefe) writes : This is a perfect example of why the C standard got it just right. Can't be, for the standard makes the mistake of specifying a real constant, to wit 0, for to mean a particular status, instead of hiding it all under macros, EXIT_SUCCESS, EXIT_FAILURE, and so on.
Technical Details
Message-ID:
<42fv9f$ld2@caip.rutgers.edu>Path:
arc1-ca.pugleaf.net!caip.rutgers.edu!not-for-mailReferences:
<jbundyDCw7uo.9sz@netcom.com> <danpop.807723059@rscernix> <42eeoo$foo@goanna.cs.rmit.edu.au>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: 4 Sep 1995 18:40:47 -0400 Organization: Rutgers University Message-ID: <42fv9f$ld2@caip.rutgers.edu> References: <jbundyDCw7uo.9sz@netcom.com> <danpop.807723059@rscernix> <42eeoo$foo@goanna.cs.rmit.edu.au> NNTP-Posting-Host: caip.rutgers.edu