Hints for writing Unix tools
mardi 21 octobre 2014 à 16:43Httqm, le 21/10/2014 à 16:43
- Consume input from stdin, produce output to stdout
- Output should be free from headers or other decoration
- Output should be simple to parse and compose
- Treat a tool’s output as an API
- Place diagnostics output on stderr
- Signal failure with an exit status
- Make a tool’s output portable
- Omit needless diagnostics
- Avoid making interactive programs
(Permalink)
- Consume input from stdin, produce output to stdout
- Output should be free from headers or other decoration
- Output should be simple to parse and compose
- Treat a tool’s output as an API
- Place diagnostics output on stderr
- Signal failure with an exit status
- Make a tool’s output portable
- Omit needless diagnostics
- Avoid making interactive programs
(Permalink)