Writing clearer Bash scripts
|
Conclusion
Some guidelines presented here may seem unnecessary. If you use them, however, you have a greater chance of writing clear Bash scripts that can easily be understood even at a much later date.
If you follow the guidelines, other programmers can work into your scripts more easily. For the sake of teamwork, agreeing on common scripting guidelines is a good idea. Additionally, adhering to these guidelines can reduce typos and errors. The standard you use is entirely up to you, as long as you stick with it.
Infos
- Google Shell Style Guide: http://google-styleguide.googlecode.com/svn/trunk/shell.xml
- Bash Style Guide and Coding Standard: http://lug.fh-swf.de/vim/vim-bash/StyleGuideShell.en.pdf
- Environmental variables: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html
- Special parameters: http://www.gnu.org/software/bash/manual/bashref.html
- GNU coding standards: http://www.gnu.org/prep/standards/
- Standard command-line options: http://tldp.org/LDP/abs/html/standard-options.html
« Previous 1 2 3 4 5 Next »
Buy this article as PDF
Express-Checkout as PDF
Pages: 4
Price $0.99
(incl. VAT)
(incl. VAT)