[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Misbehavior with constants and bash script
From: |
Quentin L'Hours |
Subject: |
Re: Misbehavior with constants and bash script |
Date: |
Mon, 19 Nov 2018 16:06:23 -0800 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 |
Hi Chet,
On 2018-11-19 03:38 PM, Chet Ramey wrote:
> When the assignment is used as an argument to `declare', it causes the
> declare command to fail, but it's not a variable assignment error, so
> the script simply continues as with any other failed command.
I remembered this email thread about declaration utilities splitting
behavior:
https://lists.gnu.org/archive/html/help-bash/2018-01/msg00006.html
If declaration utilities splitting is modified to be similar to a basic
assignment then wouldn't it make sense to do the same for the rest (in
this case assigment errors)?
It feels like POSIX progressively wants declaration builtins to have the
same rules as basic assignments, why should assignment error stay different?
--
Quentin