Quote from: DJ Omnimaga on October 25, 2010, 09:11:31 pm

In SourceCoder, I believe that if you type Copy, it recognize it as conj, so such thing may not happen in SourceCoder.

The test I just did with SourceCoder disagrees with this. That would prevent you from typing the literal string "Copy" and SourceCoder isn't designed to be an Axe source editor anyways.

Strange I thought Kerm implemented the new tokens already X.x. He said he might since he planned to make it for both Axe and BASIC.

You, getting caught using an older version of Axe? Lol

Anyways you should check out my approximately over 9000 feature requests.

Ah cool! Did you do any other calculator games and programs before? A huge RPG and an OS are both huge undertakings (I'm speaking from experience about RPGs because I made several of them back in 2001-2005), especially the later. If you are still new to programming I would probably suggest making a demo of your RPG, first, then gradually improve from it, or maybe even do a smaller prequel/side game of your RPG, to not start too big either. Otherwise, good luck!

What is the max number of labels you can have in a program? Because Runer112 was trying to help me optimize Nostalgia's menu routine and he said he got a ERR:MAX SYMBOLS. Is there anyway around this?

i think it's something like 100-150. you can always use offsets. for example instead of
[HEX]->Pic1 .player1
[HEX]->Pic2 .player2
[HEX]->Pic3 .player3
you can do
[HEX]->Pic1 .player1
[HEX]          .Pic1+8  refers to player2
[HEX]          .Pic1+16 refers to player3
etc.

Well, I meant labels like Goto LBL or sub(LBL). But the tip on static variables is helpful.

I wonder if you can use a label as a pointer, like by doing lbl123+64

You would never reliably be able to do this because future optimizations would mean that the spacing between some labels would change between every version of the parser.  This would only work if the entire routine were written with an Asm() command so you would know the length of the subroutine ahead of time.

Unfortunately there is no way around the 150 symbol limit to labels, but there are some things you can do to use less labels in general.  First of all, if you aren't calling it as a subroutine, you probably don't need it as a label.  You can instead use a combination of if's and while's to handle those situations properly (remember, most modern programming languages don't even have a goto command).  Another thing, if you have labels that are never used, comment them out becasue they still take up space on the symbol table even if they are never called.

Quote from: ASHBAD_ALVIN on October 27, 2010, 04:35:46 pm

I wonder if you can use a label as a pointer, like by doing lbl123+64

You would never reliably be able to do this because future optimizations would mean that the spacing between some labels would change between every version of the parser.  This would only work if the entire routine were written with an Asm() command so you would know the length of the subroutine ahead of time.

Unfortunately there is no way around the 150 symbol limit to labels, but there are some things you can do to use less labels in general.  First of all, if you aren't calling it as a subroutine, you probably don't need it as a label.  You can instead use a combination of if's and while's to handle those situations properly (remember, most modern programming languages don't even have a goto command).  Another thing, if you have labels that are never used, comment them out becasue they still take up space on the symbol table even if they are never called.

Quigibo, how exactly does the parser make use of memory during parsing? Have you made use of the whopping 1094 bytes of effectively safe RAM starting at $8000?