2 ms·
Well, it certainly has some strong parts, but there are some parts which are so horribly broken, that the good parts can't keep up. Just to give one example: T
by arendtio 5y ago
Well, it certainly has some strong parts, but there are some parts which are so horribly broken, that the good parts can't keep up.
Just to give one example: The topic of errexit aka `set -e`.
In the beginning, I thought it should be an easy decision and since programs are supposed to be reliable, they should terminate in case of an error. So I added `set -e` to all my scripts. However, later I learned, that if you call a function from within a condition, the function is executed without `set -e` even if the function itself sets the option. Since then, I am unsure if it is better to have a function that 'sometimes exits' when it comes across an error or 'never exists' when it comes across an error, because 'always exists' when it comes across an error does not exist.
- asah 5y agoCould one really on "always" when SIGKILL can make programs simply disappear?