PBPL 2.50b (possible) For/Next ?BUG? or just the way it is...

[mackrackit]

Doesn't happen too often, and hopefully the person it happens to can understand why it happens and how to avoid it.

Well... I kind of understand why it rolls over.

But the results when it does work has me baffled.
+-+-+-+-
Why?

[skimask]

Well... I kind of understand why it rolls over.

But the results when it does work has me baffled.
+-+-+-+-
Why?

It's overflowing WAYYY too far, flipping the sign bit, making the For/Next loop think it's still within the boundaries so it keeps adding in the next step value.
Eventually, it doesn't overflow far enough to either flip the sign bit or when it does overflow, it overflows just enough that the difference between the current count and the max (or min) and the step value goes out of the boundaries of the For/Next loop...

Doesn't make a lot of sense, does it?......

[mackrackit]

Doesn't make a lot of sense, does it?......

I wonder if the folks at MELabs knows about this?

[skimask]

I wonder if the folks at MELabs knows about this?

Probably do, but it seems to me like this particular scenario would be such an uncommon thing that a guy could either deal with it, or MeLabs could BLOAT PicBasicPro with internal checking code...ya know...like Windows. PBP seems to me like it's fairly well streamlined...I don't want/need garbage thrown in there...
I'll fire off a note to them and see what happens...actually, I'll just direct their attention to this thread....probably a lot easier.

[mackrackit]

PLEASE DO NOT MAKE PBP LIKE WINDOWS!!!

Are you sure you want to run that code?

CLICK HERE.

If you really want to run the code enter your user name and password here.

To verify it is you, enter your 83 digit PIN here.

SORRY... that number is not correct.

Would you like to send an error report?

[skimask]

Ok...That's it...You forced me into...
On that project of mine where I made the videos of the OBD2 reader...
I'm going to make a BSOD and add that into the program and the videos!