What have you found bad about bash arrays? I have some simple usage of those (in bash) and they work fine.
this post was submitted on 02 Nov 2023
34 points (97.2% liked)
Linux
48216 readers
662 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
As far as I've seen, they don't provide any advantage over a string with spaces, which doesn't work well either when you've got values with spaces:
not_what_you_think=( "a b" "c" "d" )
for sneaky in ${not_what_you_think[@]}; do
echo "This is sneaky: ${sneaky}"
done
This is sneaky: a
This is sneaky: b
This is sneaky: c
This is sneaky: d
You should put some quotes where you use the array:
not_what_you_think=( "a b" "c" "d" )
for sneaky in "${not_what_you_think[@]}"; do
echo "This is sneaky: ${sneaky}"
done
This is sneaky: a b
This is sneaky: c
This is sneaky: d
Aaaaah! Thank you kind stranger. It never would have occurred to me to quote an array!
If you run your scripts through https://shellcheck.net it'll pick up things like this. Also available as a Linux package for offline use.
I too would like to know. Thank you.
ash (and its successor dash found on other distros) is a POSIX-y shell rather than a sh clone, so it has all(? most?) of the POSIX feature set, whose syntax may indeed have been 'borrowed' from shells that came later than sh.
Not sure if there's a "parent" from which both ash and bash inherit the syntax or whether bash is the true source, but that doesn't really matter here.
All that said, it's worth checking to see if your system has a command on the PATH called [[. That has been one way that [[ support can be added to a system when the shell itself might not support it. Note that command names don't have to be alphanumeric like functions tend to be in a programming language (or other languages if you consider that the shell can be used for programming too), so [[ is perfectly valid!
Yup, that looks like exactly what was done in Alpine:
$ docker run --rm -it alpine ls -l /usr/bin/[[
lrwxrwxrwx 1 root root 12 Sep 28 11:18 /usr/bin/[[ -> /bin/busybox
So while the Ash itself doesn't support the [[ extension, this work-around produces the same effect. Nifty.
Although that link exists, that's not what is being used by default. [[ is a shell builtin in ash/busybox, so that takes precedence.
On Alpine:
❯ which [[
/usr/bin/[[
❯ command -V [[
[[ is a shell builtin
Huh. So the link is unnecessary and Ash supports [[ out of the box? Good to know, thanks!