Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -O2 -flto=auto -ffat-lto-objects -fexceptions -g
-grecord-gcc-switches -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/us
On Thu, Oct 13, 2022 at 02:35:55PM -0400, Chet Ramey wrote:
> On 10/13/22 12:47 PM, Bryan Roessler wrote:
> > For indexed arrays, yes. I hadn't made the connection with associative
> > arrays since I don't typically index them with numbers, thanks.
>
> There has to be some default, and "0" is at l
On 10/13/22 12:47 PM, Bryan Roessler wrote:
For indexed arrays, yes. I hadn't made the connection with associative
arrays since I don't typically index them with numbers, thanks.
There has to be some default, and "0" is at least consistent with indexed
arrays.
--
``The lyf so short, the craft
For indexed arrays, yes. I hadn't made the connection with associative
arrays since I don't typically index them with numbers, thanks.
$ declare -A f[0]=true
$ declare -A g[foo]=bar
$ test -v f; echo $?
0
$ test -v g; echo $?
1
On Thu, Oct 13, 2022 at 12:10 PM Chet Ramey wrote:
> On 10/13/22 12
13 Ekim 2022 Perşembe tarihinde Chet Ramey yazdı:
>
> You know that referencing an array variable without a subscript is
> equivalent to referencing element 0 (or "0").
>
Yes, but I didn't know that it applied to test -v as well.
Thanks for the reply
--
Oğuz
On 10/13/22 12:06 PM, Oğuz wrote:
test -v seems broken anyway
$ declare -A foo=(a 42)
$ declare -a bar=(42)
$ test -v foo; echo $?
1
$ test -v bar; echo $?
0
You know that referencing an array variable without a subscript is
equivalent to referencing element 0 (or "0").
--
``The lyf so sho
13 Ekim 2022 Perşembe tarihinde Chet Ramey yazdı:
> There are other ways to test whether or not an associative array has any
> set elements, but there was no way to use `*' or `@' as a key in previous
> versions.
>
test -v seems broken anyway
$ declare -A foo=(a 42)
$ declare -a bar=(42)
$ tes
On Thu, Oct 13, 2022 at 10:42:02AM -0400, Bryan Roessler wrote:
> Description:
>
> bash-5.2# declare -A a
> bash-5.2# a[foo]=bar
> bash-5.2# [[ -v a[@] ]]; echo $?
> 1
>
> bash-5.1# declare -A a
> bash-5.1# a[foo]=bar
> bash-5.1# [[ -v a[@] ]]; echo $?
> 0
>
> If this is by design I missed it.
On 10/13/22 10:42 AM, Bryan Roessler wrote:
Bash Version: 5.2
Patch Level: 2
Release Status: release
Description:
bash-5.2# declare -A a
bash-5.2# a[foo]=bar
bash-5.2# [[ -v a[@] ]]; echo $?
1
From CHANGES:
j. Associative array assignment and certain instances of referencing (e.g.,
`test
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-musl
Compiler: gcc
Compilation CFLAGS: -g -O2
uname output: Linux d1a7b22c3308 5.19.14-200.fc36.x86_64 #1 SMP
PREEMPT_DYNAMIC Wed Oct
Machine Type: x86_64-pc-linux-musl
Bash Version: 5.2
Patch Lev
On 10/12/22 10:25 AM, Chet Ramey wrote:
Then run this test script with 'errexit' option set:
$ ./bash -e test_script
test_script: line 5: pop_var_context: head of shell_variables not
a function context
It's an internal message warning that something might be wrong. We'll see
if
11 matches
Mail list logo
