Its a TI OS thingy, it restricts programs to around 8100 bytes, even though the maximum possible is around 8800 bytes.  Thats why you get the extra 600 bytes in Mirage and Ion, because they aren't stupid like TI

Hey i made my own version of Calcalc, do you mind if i post it?

Mmm using these expressions as opposed to the normal AND OR and XOR is going to be doing some fairly advanced optimizations, so its difficult to say for sure.  For now we will probably just be using them to set, erase, and toggle bits inside of 2 byte numbers.

Hah yeah i know what you mean.  This way we can debug and all the good stuff on calc, and then sign for 10-15 min when we are done and ready to upload

Since its an actual limit on executable code, its the final size of your executable, not the source. NOTE: That this does NOT include data, so your program can be larger than 8811 bytes as long as the executable code is less than 8811.  You can get around this with fancy Self Modifying Code, but i have yet to get it to work reliably.  When and If i get it to work i will definetaly post a tutorial

Exactly ^^ it fits all of my needs perfectly

Decompression is very fast in Axe with the help of the Fill() command, and in Basic it can be done while drawing the map.  Decompression for Graphmastur's would also be speedy, although maybe less so since you would be doing division and modular arithmatic on every tile.  In Axe it doesn't matter that much i wouldn't think, the differences would be very small

Hah, well when i say ill write a tutorial, i mean ill add it to the que I somehow have some free time for a bit, but i have a couple more days until school is over.