|
Size: 1203
Comment: binary data, text processing
|
Size: 2417
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| * Floating point math. Bash has only [[ArithmeticExpression|integer math]]. Use `bc(1)` or [[AWK]] instead. | 1. '''Speed'''. Do we really have to say it? Bash is slow. If speed is an important consideration, then Bash may not be the best choice. |
| Line 9: | Line 9: |
| * Associative arrays (coming in bash 4.0). Use AWK or perl or Tcl instead. | 1. '''Floating point math'''. Bash has only [[ArithmeticExpression|integer math]]. Use `bc(1)` or [[AWK]] instead. |
| Line 11: | Line 11: |
| * Fancy ProcessManagement. Bash has nothing analogous to `select(2)` or `poll(2)`. Use C instead. | 1. '''Data structures'''. Bash does not have Pascal-style records (C-style structs); nor does it have pointers. Any attempt to create advanced data structures (stacks, queues, linked lists, binary trees...) will have to be done with extremely primitive hacks. |
| Line 13: | Line 13: |
| 1. '''Fancy ProcessManagement'''. Bash has nothing analogous to `select(2)` or `poll(2)`. Use C instead. | |
| Line 14: | Line 15: |
| * XML and HTML (or alike) parsing. You'd need external tools for that, at best, use Perl. | 1. '''XML and HTML''' (or alike) parsing. You need external tools or libraries to do this correctly. Use xslt, tidy, xmlstarlet, perl, or some other suitable tool. |
| Line 16: | Line 17: |
| * Binary data, bash has no way to store the null byte, so binary data has to be encoded to be put in a variable. Parsing binary data is also a problem. Try Perl or C. | 1. '''Binary data'''. Bash has no way to store the null byte, so binary data either has to be encoded or placed awkwardly in an array. Parsing binary data is also a problem. Try perl or C. |
| Line 18: | Line 19: |
| * Text Processing. Though bash has fairly advanced string manipulation features it's not designed for this. The shell is made to run commands, if are only processing text, an AWK or perl script is going to be much much MUCH faster. If you are going to process text with bash, be sure to learn about the pitfalls associated with read. | 1. '''Database queries'''. When retrieving a tuple from a relational database, there is no way for Bash to understand where one element of the tuple ends and the next begins. In general, Bash is not suited to any sort of data retrieval that extracts multiple data values in a single operation, unless there is a clearly defined delimiter between fields. For database queries (SQL or otherwise), switch to a language that supports the database's query API. 1. '''Variable typing'''. Like most scripting languages, Bash does not really support strong variable types. Variables are loosely categorized as scalar or array, with partial support for an integer type. But really, everything is a string. 1. '''Dropping permissions'''. It can be tough to make a bash script safe to execute as root. In languages like C, perl, and python, you can easily drop privileges at a certain point. With bash, this is tricky, because while you can run su or sudo, you lose variables, and even the executing environment. Use a proper programming language if you have security worries. ---- CategoryShell |
This is a stub. Please fill in the missing pieces.
There are certain things BASH is not very good at. There are certain tasks you shouldn't do in bash, unless you really, truly have to. It's often better to switch to a different language for most of these tasks.
Speed. Do we really have to say it? Bash is slow. If speed is an important consideration, then Bash may not be the best choice.
Floating point math. Bash has only integer math. Use bc(1) or AWK instead.
Data structures. Bash does not have Pascal-style records (C-style structs); nor does it have pointers. Any attempt to create advanced data structures (stacks, queues, linked lists, binary trees...) will have to be done with extremely primitive hacks.
Fancy ProcessManagement. Bash has nothing analogous to select(2) or poll(2). Use C instead.
XML and HTML (or alike) parsing. You need external tools or libraries to do this correctly. Use xslt, tidy, xmlstarlet, perl, or some other suitable tool.
Binary data. Bash has no way to store the null byte, so binary data either has to be encoded or placed awkwardly in an array. Parsing binary data is also a problem. Try perl or C.
Database queries. When retrieving a tuple from a relational database, there is no way for Bash to understand where one element of the tuple ends and the next begins. In general, Bash is not suited to any sort of data retrieval that extracts multiple data values in a single operation, unless there is a clearly defined delimiter between fields. For database queries (SQL or otherwise), switch to a language that supports the database's query API.
Variable typing. Like most scripting languages, Bash does not really support strong variable types. Variables are loosely categorized as scalar or array, with partial support for an integer type. But really, everything is a string.
Dropping permissions. It can be tough to make a bash script safe to execute as root. In languages like C, perl, and python, you can easily drop privileges at a certain point. With bash, this is tricky, because while you can run su or sudo, you lose variables, and even the executing environment. Use a proper programming language if you have security worries.