They don’t do input checking and validation, they don’t check for errors, return codes and stuff…
No wonder their scripts fail or do something completely unexpected.
Can you blame it on the shell?
No this is not a rhetorical question: you cannot blame the shell for your negligence and incompetence.
RE:
> Can you blame it on the shell?
> No this is not a rhetorical question: you cannot blame the shell for your negligence and incompetence.
Asking largely out of confusion, I haven't completely woken up yet
yes, because the mere act of comparing two variables in bash is about 100x harder than any other language (not to mention it literally straight up adds undocumented RCE vectors to your code for example when you use [[...]])
I've settled on this, recently, for my own use:
i=$((${1} + 0)); [ "$i" -le 0 ] && { echo nope; exit; }also, you could use expr if you don't like fiddling with parentheses when dealing with numeric values.
In any case, I have never seen "best practices" for (numeric) type coercion and confirmation.
Everybody seems to come up with something on their own.
That seems worthwhile to me.
test 0 -lt "$1" 2>/dev/null || exit $?;