50 ms·
Try moving all bash code into functions leaving only global variable/constant definitions and a call to “main” at the top-level. One of my main complaints with
by Karunamon 13y ago
Try moving all bash code into functions leaving only global variable/constant definitions and a call to “main” at the top-level.
One of my main complaints with bash.. the file is evaluated in order - you can't call a function on the line before it's declared.
This fails:
#!/usr/bin/env bash
bar='bar'
foofunction
foofunction(){
echo 'foo'
echo $bar
}
Basically you have to write your entire script in reverse, and i'm unaware of a good way to get around it.
- 14113 13y agoC is the same, but at least with C it's possible to declare functions before providing definitions. Is it possible that it's the same in bash?
- xrt 13y agoI really hate writing things in reverse, but a decent style in Bash is to put everything in functions, w/ a main() at the top: #! /usr/bin/env bash set -e -u bar='bar' main() { foofunction } foofunction() { echo 'foo' echo $bar } main "$@"
- nfoz 13y agoWell, what would you do instead? It's an interpreted language. When you type "foofunction" at a prompt, you don't want it to wait around in case you define that to have meaning later. You probably want the interpreter to be smart: "Am I loading a script from a file, or am I receiving instructions interactively on the command-line?" But now there's two modes of execution, and code in a bash script won't work if you type it into the prompt yourself. That's a bit uncomfortable.