Re: uninvited members of associative array

[Ray Andrews <rayandrews@xxxxxxxxxxx>]

On 2022-12-15 18:09, Dominik Vogt wrote:
> Probability of 95% or more that the array gets modified after the
> initialisation by some stray code.  Put prints all over the place
> to find the place where the array gets modified.

Nope, I showed the output directly after the init.  If something goes 
wrong, it goes wrong during the init itself.

Lawrence:

> It makes no sense to question the code before verifying that your
data isn't garbage.

All the named keywords have exactly correct data, there's nothing not to like as far as that.  Dunno, it wouldn't be the first time that there was some silly issue in the printout, no real problem at all, so my first question assumed nothing.  My ignorance remains a deep well tho slowly getting better.

> Still not seeing a problem.

I think I'm on the scent, the array is global.  If I zero it before all the assignments (they're just numbers, no need to show the full genealogy of them), then the interlopers disappear.  So now the question is where the bogus elements come from.  They aren't actually assigned anywhere, that's for sure.  Variable crosstalk?  How does an associative array get corrupted?  Let me root around a bit ...
hey ... you don't suppose a zcurses crash might do it?