-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking Issue: Documenting Exit Codes #39
Comments
I wonder if as part of providing easy documentation on exit codes if there's a possibility for a standard set of error codes like HTTP. I think specifically having a way categorise common situations such as argument errors, file system errors, and internal errors. This could be used in a abstraction over Example error codes.
|
Didn't realize that |
You only get a byte for exit codes (portably), so numbers 400+ are out. 8 bits isn't a lot of space to pack in much information. I think 0 and 1 take care of most things, and enables the tool user to use |
This might be helpful: http://man7.org/linux/man-pages/man3/errno.3.html |
I'll assign this to me to find a place to put these docs but would eventually like to work with @yoshuawuyts to produce said docs :) |
Being able to document exit codes would be a useful for many programs, especially when reimplementing existing programs where exit codes can have special meanings.
This thread serves to gather resources about discussions happening around this topic, with the goal that eventually we'll be in a position where it's possible to document all exit codes from our programs.
Related Issues
Links
The text was updated successfully, but these errors were encountered: