[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Misbehavior with constants and bash script

From: Chet Ramey
Subject: Re: Misbehavior with constants and bash script
Date: Mon, 19 Nov 2018 19:14:11 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1

On 11/19/18 7:06 PM, Quentin L'Hours wrote:
> 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?

Because the declaration utilities distinction only matters for expansion
purposes. I'm not really interested in going beyond what posix is willing
to standardize here. The expansion and word splitting issues solve
problems; I don't see extending that to exiting as useful.

``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    address@hidden    http://tiswww.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]