Re: Misbehavior with constants and bash script

From	Quentin L'Hours <lhoursquentin@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: Misbehavior with constants and bash script
Date	2018-11-19 16:06 -0800
Message-ID	<mailman.4284.1542672394.1284.bug-bash@gnu.org> (permalink)
References	<857e2280-38c5-344e-1916-17a6c6c61b02@netsystem.de> <342c7edc-d2e3-04ec-a094-24b6c9368b97@case.edu>

Show all headers | View raw

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

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: Misbehavior with constants and bash script Quentin L'Hours <lhoursquentin@gmail.com> - 2018-11-19 16:06 -0800

csiph-web