Exit codes #2

New Issue

kj7rrv · 2022-11-30T12:32:08-08:00

kj7rrv commented

2022-11-30 12:32:08 -08:00

Processes should have exit codes that can be waited for by other processes. Tracking parent/child processes is not needed; it won't be a problem for any process to wait for any other process by PID (like is currently possible), but get the exit code.

The shell should eventually be as POSIX-like as possible, so POSIX-style numeric exit codes are needed. However, for extra flexibility, being able to also use strings would be helpful (e.g. (0, "success") or (1, "configuration file syntax error")).

Processes should have exit codes that can be waited for by other processes. Tracking parent/child processes is not needed; it won't be a problem for any process to wait for any other process by PID (like is currently possible), but get the exit code. The shell should eventually be as POSIX-like as possible, so POSIX-style numeric exit codes are needed. However, for extra flexibility, being able to also use strings would be helpful (e.g. `(0, "success")` or `(1, "configuration file syntax error")`).

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kj7rrv/fibonaccios#2