diff options
| author | Thien-Thi Nguyen <ttn@gnuvola.org> | 2004-05-12 14:39:34 +0000 |
|---|---|---|
| committer | Thien-Thi Nguyen <ttn@gnuvola.org> | 2004-05-12 14:39:34 +0000 |
| commit | f87899ebd6ec1afeeaecefdc4ac4040740fc8c05 (patch) | |
| tree | e08174b6f4b548fdb7dfdae8205dad754d48c9c1 | |
| parent | d6696bb69c690f3bc2f4be8de55352b1928d528e (diff) | |
New entry re clamping to EXIT_FAILURE.
| -rw-r--r-- | admin/notes/exit-value | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/admin/notes/exit-value b/admin/notes/exit-value index 2eb598bf49..e59bb614b9 100644 --- a/admin/notes/exit-value +++ b/admin/notes/exit-value @@ -21,3 +21,15 @@ value requirements outlined in the first paragraph! That is the job of the #endif Values aside from EXIT_SUCCESS and EXIT_FAILURE are tricky. + + + +ttn 2004-05-12 + +Values aside from EXIT_SUCCESS and EXIT_FAILURE can be used to indicate +finer gradations of failure. If this is the only information available +to the caller, clamping such values to EXIT_FAILURE loses information. +If there are other ways to indicate the problem to the caller (such as +a message to stderr) it may be ok to clamp. In all cases, it is the +relationship between the program and its caller that must be examined. +[Insert ZAMM quote here.] |