Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #14832 > unrolled thread

Re: Misbehavior with constants and bash script

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Misbehavior with constants and bash script Chet Ramey <chet.ramey@case.edu> - 2018-11-19 19:14 -0500

#14832 — Re: Misbehavior with constants and bash script

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    chet@case.edu    http://tiswww.cwru.edu/~chet/

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web