[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Final backslash<newline> causes array assignment mis-parse in previo
From: |
Chet Ramey |
Subject: |
Re: Final backslash<newline> causes array assignment mis-parse in previous eval |
Date: |
Tue, 26 Aug 2014 16:06:07 -0400 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
On 8/25/14, 6:25 PM, jim.avera@gmail.com wrote:
> Bash Version: 4.3
> Patch Level: 0
> Release Status: release
>
> Description:
> NOTE: This repeats (approximately) a bug I sent a few minutes ago, but
> with
> an invalid From: address. Most likely my ISP dropped the message as
> spam,
> but if not, please accept my appoligies for the dup.
>
> \<newline> is supposed to be effectively ignored, but if it appears at
> the
> end of the script then parse errors sometimes occur with previous
> statements.
> In particular eval "array=(values...)" is mis-parsed if a subsequent
> statement
> ends with <backslash><newline> and there is nothing further in the script.
Thanks for the report. This will be fixed in the next release of bash.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/