Date:Fri, 29 Mar 2019 08:41:49 -0400
From:Greg Wooledge
Message-ID: <20190329124148.a3t3xkze4btsk...@eeg.ccf.org>
| But perhaps you're right about the letter C specifically.
I was, because that was the character of relevance in the bug
report, and solving (or inven
On 3/27/19 9:06 AM, joerg...@snafu.de wrote:
> Bash Version: 4.2
> Patch Level: 46
> Release Status: release
>
> Description:
> If I declare a global read-only variable and I try to declare a local
> variable with that name, I can not create
> the local variable.
> I expect tha
On Wed, Mar 27, 2019 at 02:06:51PM +0100, joerg...@snafu.de wrote:
> If I declare a global read-only variable and I try to declare a local
> variable with that name, I can not create
> the local variable.
> I expect that local variables can be declared independently for the
> gl
> | [A-Z] isn't safe to use unless ...
>
> That's true to an extent, but we know here that the intent is to
> match 'C' which is between A and Z in every locale in the universe.
> Variations on A might not be, variations on Z might not be, and there
> might be more than just the upper case Engli
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
> | And you forgot to quote.
>
> Really! That again! Here, unless one of A or B (or perhaps C,
> though as that's supposed to be removed, it shouldn't matter) is in
> IFS - in which case I think we'd be told - quoting makes no difference
> at all.
The example is clearly contrived just for t
Date:Thu, 28 Mar 2019 17:27:24 -0400
From:Greg Wooledge
Message-ID: <20190328212724.aczkwjoyceeg6...@eeg.ccf.org>
| You have two problems here. Well, four really.
2 really, I think...
| First, your first example invokes platform-defined behavior.
Technically,
