Hello,

I think I have found some unexpected behavior related to constants in
bash scripts. I have attached the short proof of concept bash script.

Usually bash scripts continue when they face an error with one command
but this script shows some weired behavior. It exits all the functions
it has called without executing the remaining commands and the continues
to run in the top scope of the script.

This only happens when a constant declared with
declare -r myConst="myConstantValue"
is attempted to be redefined using
myConst="new value"
but not with
declare myConst="new value"

This behavior doesn't seem right.

I have tried this on Ubuntu 16.04 LTS with bash version
GNU bash, Version 4.3.48(1)-release (x86_64-pc-linux-gnu)

Cheers,
Alex
#!/bin/bash
function foo
{
        echo "A"
        declare -r vconst="I am fixed."
        echo "B"
        declare vconst="new value"
        echo "C"
        unset vconst
        echo "D"
        vconst="new value"
        echo "E"
}

function bar
{
        echo "before foo"
        foo
        echo "after foo"
}

function buzz
{
        echo "before bar"
        bar
        echo "after bar"
}

foo
bar
buzz
echo "the last line"

<<attachment: alexander_reintzsch.vcf>>

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to