diff options
| author | Simon McVittie <smcv@collabora.com> | 2021-02-25 12:22:23 +0000 |
|---|---|---|
| committer | Simon McVittie <smcv@collabora.com> | 2021-02-25 12:22:34 +0000 |
| commit | 2db42705a7e413953d26930880951734ab0df931 (patch) | |
| tree | 4ef7a5f1f7973a142ab4edafe8d2969ddbc5d778 /glib/gmain.c | |
| parent | 6259fb5be7f727fba1507315f79791ee0f2dee66 (diff) | |
| download | glib-wip/wait-status.tar.gz | |
Distinguish more clearly between wait status and exit statuswip/wait-status
On Unix platforms, wait() and friends yield an integer that encodes
how the process exited. Confusingly, this is usually not the same as
the integer passed to exit() or returned from main().
I find that it's clearer what is going on if we are consistent about
referring to the result of wait() as a "wait status", and the value
passed to exit() as an "exit status".
GSubprocess already gets this right: g_subprocess_get_status() returns
the wait status, while g_subprocess_get_exit_status() genuinely returns
the exit status. However, the GSpawn family of APIs has tended to
conflate the two.
Confusingly, g_spawn_check_exit_status() has always checked a wait
status, and it would not be correct to pass an exit status to it.
Deprecate it in favour of g_spawn_check_wait_status(), which does
the same thing.
Signed-off-by: Simon McVittie <smcv@collabora.com>
Diffstat (limited to 'glib/gmain.c')
| -rw-r--r-- | glib/gmain.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/glib/gmain.c b/glib/gmain.c index 15581ee7a..d82683ed6 100644 --- a/glib/gmain.c +++ b/glib/gmain.c @@ -5723,7 +5723,7 @@ g_child_watch_source_new (GPid pid) * you will need to pass #G_SPAWN_DO_NOT_REAP_CHILD as flag to * the spawn function for the child watching to work. * - * In many programs, you will want to call g_spawn_check_exit_status() + * In many programs, you will want to call g_spawn_check_wait_status() * in the callback to determine whether or not the child exited * successfully. * |