aboutsummaryrefslogtreecommitdiffstats
path: root/admin/notes/exit-value
diff options
context:
space:
mode:
authorThien-Thi Nguyen2004-05-09 12:38:56 +0000
committerThien-Thi Nguyen2004-05-09 12:38:56 +0000
commit41d8e8b29d7adb12c26f3dae73a1f9ff56f10233 (patch)
tree51c27bc15d78d4c0e51bbcba65d25943e37a41d7 /admin/notes/exit-value
parent07312b25d351a9c9b91906321f07a7fc0754b660 (diff)
downloademacs-41d8e8b29d7adb12c26f3dae73a1f9ff56f10233.tar.gz
emacs-41d8e8b29d7adb12c26f3dae73a1f9ff56f10233.zip
Initial revision
Diffstat (limited to 'admin/notes/exit-value')
-rw-r--r--admin/notes/exit-value23
1 files changed, 23 insertions, 0 deletions
diff --git a/admin/notes/exit-value b/admin/notes/exit-value
new file mode 100644
index 00000000000..2eb598bf495
--- /dev/null
+++ b/admin/notes/exit-value
@@ -0,0 +1,23 @@
1ttn 2004-05-09
2
3The exit value of a program returning to the shell on unixoid systems is
4typically 0 for success, and non-0 (such as 1) for failure. For vms it is
5odd (1,3,5...) for success, even (0,2,4...) for failure.
6
7This holds from the point of view of the "shell" (in quotes because vms has a
8different dispatch model that is not explained further here).
9
10From the point of view of the program, nowadays stdlib.h on both type of
11systems provides macros `EXIT_SUCCESS' and `EXIT_FAILURE' that should DTRT.
12
13NB: The numerical values of these macros DO NOT need to fulfill the the exit
14value requirements outlined in the first paragraph! That is the job of the
15`exit' function. Thus, this kind of construct shows misunderstanding:
16
17 #ifdef VMS
18 exit (1);
19 #else
20 exit (0);
21 #endif
22
23Values aside from EXIT_SUCCESS and EXIT_FAILURE are tricky.