> In the following example, I was expecting var2 not to be seen as an unbound
> variable after it was declared. Wouldn't it be more consistent with the
> treatment of var1 not to issue the unbound variable error in this case? What
> is the rationale behind the current behavior?
>
> bash-
In the following example, I was expecting var2 not to be seen as an unbound
variable after it was declared. Wouldn't it be more consistent with the
treatment of var1 not to issue the unbound variable error in this case? What
is the rationale behind the current behavior?
bash-3.2$ shopt -
In the following example, I was expecting var2 not to be seen as an unbound
variable after it was declared. Wouldn't it be more consistent with the
treatment of var1 not to issue the unbound variable error in this case? What
is the rationale behind the current behavior?
bash-3.2$ shopt -s
