aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--build2/test/script/script23
1 files changed, 12 insertions, 11 deletions
diff --git a/build2/test/script/script b/build2/test/script/script
index 1127fb3..9fb2a28 100644
--- a/build2/test/script/script
+++ b/build2/test/script/script
@@ -48,23 +48,24 @@ namespace build2
struct command_exit
{
- // C/C++ don't apply constraints to program exit code values other than
- // being of int type.
+ // C/C++ don't apply constraints on program exit code other than it
+ // being of type int.
//
// POSIX specifies that only the least significant 8 bits shall be
// available from wait() and waitpid(); the full value shall be
- // available from waitid() (read more at
- // http://pubs.opengroup.org/onlinepubs/9699919799/functions/_Exit.html).
- // While Linux man page for waitid() doesn't mention any deviations
- // from the standard the FreeBSD implementation (as of version 11.0)
- // only returns 8 bits like the other wait*() calls.
+ // available from waitid() (read more at _Exit, _exit Open Group
+ // spec).
+ //
+ // While the Linux man page for waitid() doesn't mention any
+ // deviations from the standard, the FreeBSD implementation (as of
+ // version 11.0) only returns 8 bits like the other wait*() calls.
//
// Windows supports 32-bit exit codes.
//
- // Note that in shells some exit values can have a special meaning so
- // using them can be a source of confusion, For bash values in the
- // [126, 255] range are such a special ones (read more at
- // http://tldp.org/LDP/abs/html/exitcodes.html).
+ // Note that in shells some exit values can have special meaning so
+ // using them can be a source of confusion. For bash values in the
+ // [126, 255] range are such a special ones (see Appendix E, "Exit
+ // Codes With Special Meanings" in the Advanced Bash-Scripting Guide).
//
exit_comparison comparison = exit_comparison::eq;
uint8_t status = 0;