Re: unassigned/untyped behaviour

[arnold]

Code and documentation updates are now pushed to Git.

Thanks all,

Arnold

M <c24p0101@gmail.com> wrote:

> Il giorno mar 21 nov 2023 alle ore 20:32 <arnold@skeeve.com> ha scritto:
>
> > Hi All.
> >
> > I finally took at look at this.  "M", thanks for the
> > report.  Andy, thanks for the test case.
> >
> [...]
> > Yes, there's a difference of behavior in that `a' is unassigned
> > and `a[1]' becomes a number, but "fixing" that is next to impossible
> > given the way Node_elem_new works.  Forcing numeric or string
> > type is the next best thing.
> >
> > I will work on the documentation. Here is a code fix
>
>
> Hi, thanks for the fix!
> I had imagined it would be complicated to "fix" the behaviour both in the
> array and non-array cases, anyway how it works now is certainly clearer to
> understand and to use.
>
> thanks,
> M.
>
>
>
> -- 
> me -> http://crap0101.altervista.org/