was set, not when it was being
looked up. Obviously, it won't find a match if the name is invalid, so
this may have been seen as an optimization. But in this case, it would
simply be better to return nothing and do nothing, not throw an error.
The name does not NEED to be valid here.
Anyway, that my guess :)
Thanks for looking into it,
Regards,
Christopher Barry
Rajant
On Wed, 7 Mar 2018 09:51:59 -0500
Chet Ramey wrote:
> On 3/6/18 11:38 PM, christopher barry wrote:
>
> > Bash Version: 4.4 (does not work)
> > Patch Level: 12
> > Release Status: release
> >
> >
> > Description:
> >
> > a simple fun
On Wed, 7 Mar 2018 11:09:10 -0500
Greg Wooledge wrote:
> On Wed, Mar 07, 2018 at 10:54:22AM -0500, christopher barry wrote:
> > So yes 'ivar -3' is very, very bad indeed, and was a nasty bug, and
> > I absolutely agree that making sure the string is a validly
>
On Wed, 7 Mar 2018 11:45:13 -0500
christopher barry wrote:
===8<---snip
>
> I am in fact using this method with associative arrays.
>
> I have a default hash that is full of default values for a particular
> generic type of thing. Variations of this thing use many of the
&g
On Fri, 9 Mar 2018 11:29:35 -0500
Chet Ramey wrote:
> On 3/7/18 3:20 PM, christopher barry wrote:
> > On Wed, 7 Mar 2018 11:45:13 -0500
> > christopher barry wrote:
> >
> > ===8<---snip
> >
> >>
> >> I am in fact using this method wi
