Axe doesn't have sin() and cos() yet.  I'm adding those when I switch to singed numbers.  Builderboy used the first 2 terms of the taylor series expansion of sin to get approximations.  That's probably why the code doesn't make much sense at first glance.  If you haven't taken calculus then its probably best you wait until I get the trig functions supported becasue the actual math involved is a lot more complicated.

I was planning to add an instr() command, but a little more general than what you are referring to.  It would be like this:

instr(START,BYTE<,SIZE>)

The last option is optional.  You give it a pointer, and it searches for the byte until it finds it and then returns the pointer to that byte, or it returns zero if not found.  That way, its not just limited to application variables, you can use it anywhere.

Its pretty easy to add, but I haven't yet because honestly, it really isn't as useful as it sounds.  There is a regular assembly instruction that does exactly this called "cpir" but I've never used it or needed to use it ever for anything.  I've almost never seen it used in other programs either.  It would only be needed for very specific applications, and even then its easy to write a subroutine yourself with existing commands.  But yes, I will support it eventually, but its in the back of my list.

I might be able to write an encryption algorithum eventually.  I'll explain in detail later how to use the new features in the program, I was just too tierd last night.

Just beware the new commands are kind of vulnerable to change since I'm not sure exactly how I'll generalize them to other variables in the future.

Hopefully so  And Quigibo, did you ever find this?

I was never able to replicate that one unfortunately.  I assumed it was a fluke in the calculator.  If you find yourself getting that error again, I'll take a look at the source file.  I know it would be hard in this circumstance since it could freeze the parser and/or clear the ram, but you can try archiving it before parsing it so a reset doesn't delete it.

EDIT: 256th post! All my posts can be counted by a single byte!

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.

Yeah, hexadecimal doesn't exist if you don't want it to.  You can just think of it as base 10 if you want.  You can even think about it in base 3, or 4, or 255, or 9000, whatever you want!  As long as you understand a number is a number no matter what base you write it in.

This is what you should do if you want to use decimal:
ΔList(8,9,10,11,12)->GDB1

Instead of doing this:
[08090A0B0C]->GDB1

They are both identical.


EDIT: and by the way, this is correct:

:{GDB1}+1->{GDB1}

Not any of these:

:{GDB1}+1->GDB1
:GDB1+1->GDB1
:GDB1+1->{GDB1}

The last one is syntactically correct, but it won't do what you're trying to make it do.

And nice trick Quigibo I didn't realise that it should be easier for coding menus.

You can use that for menus, but then you can't have auto scrolling.  You know where if you hold down one of the arrows for a second, it starts automatically scrolling for you by registering that key press a bunch of times.  I think the regular "getkey" is probably better for menus since its simpler to use and you don't need a quick response or multiple key presses anyway.

Heh, Dj what you just did is RLE

Yeah I was about to say that lol.  That's a good idea.  It would be quite easy to add too, but maybe a little advanced for most users and it would absolutely require a helper tool or a sketch on paper.  Its not just sprites you can compress.  Level data, text and even entire programs can potentially be compressed if they're sparse enough.