Array glitch

[Peter Haworth]

Terry,
I tried your script here and got the same error as you in LC 5.5.4 and LC
Community 6.0 on a Windows 8 box.

I use strict compile mode but declaring the tSimpleArray variable made no
difference.  I also put the seconds into a variable, tKey, put zero into
tSimpleArray[tKey], then did a put tSImpleArray[tKey] and the message box
happily showed zero.

My guess is that it's a problem within the debugger while formatting the
value of the key for display and nothing to do with regular access of the
array key contents

A quick search of the QCC turned up a couple of debug/array abort issues
but none that match something as simple as this situation, so you're best
bet to get to the bottom of it is file a bug report.

Pete
lcSQL Software <http://www.lcsql.com>


On Thu, Jul 11, 2013 at 6:31 PM, Terry Dennis
<tedennis at softwaredetails.com>wrote:

> Mark: re: test script in a button in a *new stack*?
>
> Been there, done that.  As I noted in a prior email, it occurred ...
>
> "3) in an entirely new stack after exiting and re-entering LC"
>
> Perhaps I'm being paranoid and I shouldn't worry about it.
>
> If I rely on that assumption as a basis for using seconds as my data
> access scheme, it's likely I will regret it somewhere down the road.
>
> I think Murphy is in my family tree.
>
> I've considered using the difference between "seconds" and the start of
> the decade, or the start of the century, as my array key.  Then, adjust it
> when necessary.  But, until I can be reasonably confident I won't run into
> the same type of problem with a different value, I'm reluctant to rework my
> logic to use that scheme.
>
> I suppose I could spend a bunch of time running a zillion tests with
> different values until I come across the value that breaks it.   Then we
> would have something for the LC guys to work on.  I'll get back to you in a
> couple of years to let you know the results of my tests.  ;-)
>
> Of course, it could be it has nothing whatsoever to do with the value of
> the key ... which is why I didn't think "seconds" would break it.
>
> Loop: See "recursive"
>
> Recursive: See "loop"
>
> Terry
>
> ______________________________**_________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/**mailman/listinfo/use-livecode<http://lists.runrev.com/mailman/listinfo/use-livecode>
>