So i had a great idea!  Why not use InData() to search for trigger tokens in the program to be optimized?  I tested an 8000 bytes file and it could search through the entire file in less than a second!  This means possibility for lightning fast optimization!

Hmm i just have to remember that using this method ignores strings, so that when i find a token to optimize, i will have to search backwards in the file to determine if its inside a string or not.  This also makes the loading bar a lot harder to implement since all the time spent searching will be spent in a single command.  Hmmmm i shall see how fast everything is

Wow that sounds promising, you should try it!

Wow, that is FAST!

And 8000 KB/s is about twice Axe's speed, so yeah, a loading bar is probably not needed. A loading message should be fine, and personally, I think a percentage counter is a good idea, just so that people optimizing a 20 KB program wouldn't think it froze after 2.5 seconds. Doesn't matter two much, though.

EDIT: Can I have a demo just for a quick test?

EDIT2: Wow, I meant 8 KB/s. If it were 8000, that'd be absolutely amazing for anything Z80

Unfortunately no form of percentage can be calculated but i think it will be fast enough Currently i have no real working code however so i cant give anything out I did document all the optimizations i currently am implementing and they are up to 12

As for the (A-B)*5->C, it currently isn't smart enough to do things like that, and i imagine getting it to the point where it can recognize expressions like that would be crazy hard to do, but if i figure out a way to do it, hells yeah i will

Garrg, so there are a lot of sneaky things happening now So InData stops as soon as it finds a 0, since thats the definition of the end.  BUT what about 2 byte tokens?  for example Str1 has a 0 as its second byte, so the optimizar treats that as the end of the program.  So now before it parses the program it goes through and changes all the 0's into 60, which is unused in all two byte tokens.  Then when the program is finished, it goes back and changes all the 60's back into 0's. lol

EDIT: Grrr but that means that it would mess up hacked variables.  Hmmm i will have to think about this some more...

EDIT2: Yay got it to work, if it quits and it finds that its not at the end of the file, it scratches its head and turns around and goes back into the search loop ^^

Nice that you got it sorted out.