Well, back to my original question ... how do I determine what caused this?
If the debugger chokes on it, there's a good chance there's some other
insidious related glitch in the guts of LC that will cause other strange
happenings. I'm allergic to strange happenings.
I don't want to use a value for my array keys that will cause nightmarish
problems in the future.
I built that test script to isolate a problem that had already cost me a
bunch of time and caused a loss of data. Then, isolating the problem took a
while, because I didn't think something as simplistic as that would be a
problem.
Now, does anybody have any idea what the problem is, so I can redesign my
array to avoid the problem? Or, better yet, have somebody at RunRev fix the
problem so some other poor schmuck doesn't experience the same surprise.
That glitch exists in:
1) an existing stack (which is how I first encountered it),
2) in the same stack with a new button and new script,
3) in an entirely new stack after exiting and re-entering LC.
I don't think it's environmental, but I suppose it could be ... which brings
me back to my original question ... how do I determine what caused this?
Terry
From: Mark Wieder <mwie...@ahsoftware.net>
To: use-livecode@lists.runrev.com
Subject: Re: Array glitch
Message-ID: <16481125456.20130711150...@ahsoftware.net>
Content-Type: text/plain; charset=us-ascii
Jacque-
Thursday, July 11, 2013, 2:07:04 PM, you wrote:
What's the bug exactly? Big numbers as keys?
Oops. I can't find the bug I was thinking about at the moment, but it
turns out I was thinking of another reported bug.
I tried the test script here and it worked fine.
--
-Mark Wieder
mwie...@ahsoftware.net
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
