Mercurial > emacs
annotate admin/notes/exit-value @ 99682:ea8cf739773d
* international/mule-cmds.el (update-leim-list-file): Simplify.
(prefer-coding-system, find-coding-systems-for-charsets):
Fix docstring typos.
(select-safe-coding-system, input-method-exit-on-first-char)
(language-info-alist, language-info-custom-alist): Reflow docstrings.
(toggle-input-method, read-multilingual-string): Doc fixes.
Reflow docstrings.
(locale-name-match, sort-coding-systems, find-multibyte-characters)
(read-char-by-name): Use `string-match-p'.
(get-char-code-property, put-char-code-property)
(char-code-property-description): Be silent while loading uni-* files.
(ucs-names): Use `dotimes-with-progress-reporter', because loading
the Unicode character names is *slow*.
author | Juanma Barranquero <lekktu@gmail.com> |
---|---|
date | Tue, 18 Nov 2008 01:35:25 +0000 |
parents | dc9bd6dd0d8d |
children |
rev | line source |
---|---|
55463 | 1 ttn 2004-05-09 |
2 | |
3 The exit value of a program returning to the shell on unixoid systems is | |
4 typically 0 for success, and non-0 (such as 1) for failure. For vms it is | |
5 odd (1,3,5...) for success, even (0,2,4...) for failure. | |
6 | |
7 This holds from the point of view of the "shell" (in quotes because vms has a | |
8 different dispatch model that is not explained further here). | |
9 | |
10 From the point of view of the program, nowadays stdlib.h on both type of | |
11 systems provides macros `EXIT_SUCCESS' and `EXIT_FAILURE' that should DTRT. | |
12 | |
13 NB: The numerical values of these macros DO NOT need to fulfill the the exit | |
14 value 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 | |
23 Values aside from EXIT_SUCCESS and EXIT_FAILURE are tricky. | |
55552
dc9bd6dd0d8d
New entry re clamping to EXIT_FAILURE.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents:
55463
diff
changeset
|
24 |
dc9bd6dd0d8d
New entry re clamping to EXIT_FAILURE.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents:
55463
diff
changeset
|
25 |
dc9bd6dd0d8d
New entry re clamping to EXIT_FAILURE.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents:
55463
diff
changeset
|
26 |
dc9bd6dd0d8d
New entry re clamping to EXIT_FAILURE.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents:
55463
diff
changeset
|
27 ttn 2004-05-12 |
dc9bd6dd0d8d
New entry re clamping to EXIT_FAILURE.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents:
55463
diff
changeset
|
28 |
dc9bd6dd0d8d
New entry re clamping to EXIT_FAILURE.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents:
55463
diff
changeset
|
29 Values aside from EXIT_SUCCESS and EXIT_FAILURE can be used to indicate |
dc9bd6dd0d8d
New entry re clamping to EXIT_FAILURE.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents:
55463
diff
changeset
|
30 finer gradations of failure. If this is the only information available |
dc9bd6dd0d8d
New entry re clamping to EXIT_FAILURE.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents:
55463
diff
changeset
|
31 to the caller, clamping such values to EXIT_FAILURE loses information. |
dc9bd6dd0d8d
New entry re clamping to EXIT_FAILURE.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents:
55463
diff
changeset
|
32 If there are other ways to indicate the problem to the caller (such as |
dc9bd6dd0d8d
New entry re clamping to EXIT_FAILURE.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents:
55463
diff
changeset
|
33 a message to stderr) it may be ok to clamp. In all cases, it is the |
dc9bd6dd0d8d
New entry re clamping to EXIT_FAILURE.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents:
55463
diff
changeset
|
34 relationship between the program and its caller that must be examined. |
dc9bd6dd0d8d
New entry re clamping to EXIT_FAILURE.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents:
55463
diff
changeset
|
35 [Insert ZAMM quote here.] |