Does anyone know why "X>0" makes an endless loop?

sure, I was writing a falldown game and I needed to check if Y was greater than 0, if it was greater I would subtract one from it.  So basicly
repeat F
If Y>0
Y-1-->Y
end
endexcept that F is set by something and there's a couple more conditions, but they are kinda irrelevant

I'm sorry, I would if I could but I just lost conectivity with TI-connect, and I can't find the cd for the drivers.  I'm still trying to get that fixed.

The bug described here goes a little deeper than I thought.  I still haven't found it yet, but I'm almost certain what's happening is that the 2 passes the parser makes are getting out of sync.  Normally, the 2nd pass has to follow the code exactly identically to the first pass but without actually writing anything so that static pointers can be replaced with their correct locations.  When they get out of sync, the 2nd pass starts writing those pointers over the wrong locations, in this case, over a subroutine call causing the program to call some random location in memory which causes the freeze.

I haven't added many new features yet because I need to get this resolved first, just in case it would force me to change any new code.  Hopefully I will locate the exact problem tomorrow and have added enough new features for a Sunday night update.  I'll keep you all posted. Just wanted to let everyone know whats been going on.

You have no idea... I spent about 5 straight hours searching today... I couldn't find the error... and then finally... I found it, and it took 30 seconds to fix.  *face palm*  That's the worst thing about bugs.  Once you know whats wrong, its easy to fix but actually finding that bug is a nightmare, especially in a parser where you have switch statements with hundreds of arguments and tons of subroutines that are intertwined with each other so much, that a tiny change in one affects everything else.

Anyway, the resolution is a bit too complicated to explain, but the issue is resolved now.  I'll post an update late tonight.  This has been the hardest bug yet!

EDIT.

You have no idea... I spent about 5 strait hours searching today... I couldn't find the error... and then finally... I found it, and it took 30 seconds to fix.  *face palm*  That's the worst thing about bugs.  Once you know whats wrong, its easy to fix but actually finding that bug is a nightmare, especially in a parser where you have switch statements with hundreds of arguments and tons of subroutines that are intertwined with each other so much, that a tiny change in one affects everything else.

Yup. Sometimes it takes even longer to fix. In a school VB project I spent 10-12 hours on a bug once  and I heard people spend even more. Finally, the bug was just a little inverted < boolean logic symbol . In some cases, I invert two variable storage.

In assembly it must be even worse because you code on the PC then have to load everything on an emulator all the time and test programs. Good job and I hope you don't encounter too many of those bugs

Another annoying bug is the kind of bug that is hard to recreate and happens randomly. It's hectic because to fix it you have to know what exactly causes it . In the Reign Of Legends 3, when riding the airship on the overworld map, in some cases, when riding it on next map, you get an ERR:DOMAIN error, but it only ever happened twice to me in a matter of 4 years. Because of this I never bothered fixing it cuz I was unable to figure out

Raylin is pleased to hear about an Axe update.
Raylin understands your plight about bugs.
Raylin remembers a time where he wrote a 3000+ line program and had to find the bug in it. It was a missing semicolon.

Raylin is talking in third person for some odd reason.