Sujet : Re: Command Languages Versus Programming Languages
De : ldo (at) *nospam* nz.invalid (Lawrence D'Oliveiro)
Groupes : comp.unix.shell comp.unix.programmer comp.lang.miscDate : 30. Mar 2024, 02:15:29
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <uu7p3g$k1e9$3@dont-email.me>
References : 1 2 3 4 5 6
User-Agent : Pan/0.155 (Kherson; fc5a80b8)
On Sat, 30 Mar 2024 01:30:53 +0100, Janis Papanagnou wrote:
Besides the naming, keep in mind that there's a semantical differences
between a "command", a "built-in command", and "shell construct". An
example where you can observe operational differences is:
'/bin/test' and '/bin/['
'test' and '['
'[['
where (for example) the latter does not need quoting.
I know that there are places in POSIX shells where the usual rules for
interpretation of special-substitution markers are altered or suspended.
But those situations are always delimited in some special way (distinctive
syntactic constructs or reserved words). Throughout the entire rest of the
language, the principles I have described still apply.