Ben Bacarisse
5/19/2015 12:20:00 AM
jonas.thornvall@gmail.com writes:
> Den tisdag 19 maj 2015 kl. 00:40:33 UTC+2 skrev jonas.t...@gmail.com:
>> Den tisdag 19 maj 2015 kl. 00:19:02 UTC+2 skrev jonas.t...@gmail.com:
>> > Den måndag 18 maj 2015 kl. 23:53:56 UTC+2 skrev Michael Haufe (TNO):
>> > > On Monday, May 18, 2015 at 3:34:31 PM UTC-5, jonas.t...@gmail.com wrote:
>> > > > Is there a way to trace where an iteration do lockup in a javascript?
>> > > > Could they not printout the row executed when you break script?
>> > >
>> > > In the Firefox debugger you can tell it to pause on
>> > > exceptions. I suspect the other popular browsers support this
>> > > functionality as well.
>> >
>> > I just implemented a counter, and get strange maybe even impossible result.
>> >
>> > I use base 11 and start to convert from 0 using a counter.
>> >
>> > But the program decides to loop at different numbers at different
>> > executions, is that even possible?
>> >
>> > Javascript is not threaded, it is linear execution?
>>
>> It do bug out at 29 ones or nines. But when i use a counter it can
>> bug out on any number between 117-1000
>
> If i just could find the smallest number it bugs out for in base 11.
> But the counter approach does not work because it locks up on
> different numbers different execution which to me is ape weird.
Your code has reached the point where it is no longer comprehensible
even to you, its author. I think you need to spend a portion of the
time on this project to learning how to program.
--
Ben.