2015年2月24日 · We can say that yes, it is a programming language. According to man bash, Bash is a "sh-compatible command language". Then, we can say a "command language" is "a programming language through which a user communicates with the operating system or an application". From man bash: DESCRIPTION

Here in Bash, the two statements yielding "yes" are pattern matching, other three are string equality:

2021年10月27日 · See Bash Shell Programming. Share. ... an 'if' condition is executed in a mainstream programming ...

2024年12月14日 · Bash (Bourne again shell) is a shell replacement for the Bourne shell. Bash is superset of sh. Bash supports sh. POSIX is a set of standards defining how POSIX-compliant systems should work. Bash is not actually a POSIX compliant shell. In a scripting language we denote the interpreter as #!/bin/bash. Analogy:

2012年9月14日 · Most of the above can be found under Special Parameters in the Bash Reference Manual. Here are all the environment variables set by the shell. For a comprehensive index, please see the Reference Manual Variable Index .

However, because you so often want to perform comparisons and other operations that would be Boolean expressions in regular non-shell programming languages, there is a special command that you can run to do those. It used to be a separate binary, but these days it's built into the shell.

2013年4月4日 · What I feel uneasy about, is this recommendation from Bash pitfalls. In addition to this, the use of ls is just plain unnecessary. It's an external command whose output is intended specifically to be read by a human, not parsed by a script. This is even more intimidating and lapidary (from the same link as above):

Object oriented programming In bash, you cannot do object oriented programming, unless you build a quite complex system of allocation of objects (I thought about that. it's feasible, but insane). In practice, you can however do "Singleton oriented programming": you have one instance of each object, and only one.

2010年11月15日 · Variables and arrays (indexed or associative*) in Bash are always strings by default, but you can use flags to the declare builtin, to give them attributes like "integer" (-i) or "reference"** (-n), which change the way they behave. Bash arithmetic accepts ASCII/string numbers for input, so there are few reasons to actually use the integer ...

Now, shell scripting does span the boundary between programming and using the system, so this could be on topic on either site. If there were a question about "how do I set up networking", that would definitely belong on Unix/Linux. If it were a question about interactive keybindings in Bash, that would also belong there.