|
Size: 690
Comment: Added XML parsing.... As master commanded.
|
Size: 1203
Comment: binary data, text processing
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| Line 14: | Line 15: |
* 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. * 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. |
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.
Floating point math. Bash has only integer math. Use bc(1) or AWK instead.
- Associative arrays (coming in bash 4.0). Use AWK or perl or Tcl instead.
Fancy ProcessManagement. Bash has nothing analogous to select(2) or poll(2). Use C instead.
- XML and HTML (or alike) parsing. You'd need external tools for that, at best, use Perl.
- 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.
- 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.