Really what I would like to see is a graphing calc that is as powerful as possible while still be classroom and test certified. Because with the professional edition we are dealing with a very small market of pure calc gamers like us. but the standard edition ought to be enjoyed by all. 

Unfortunately she is going to my sister's high school next year. So I will be sure to proliferate anti-Friday Prizm progs to my sister next year.

Nice there and welcome on the forums. Unfortunately I don't speak either German or Latin, but I know we have several other users who do.   

Note: Next time you create a topic please don't lock unless you require that others must not post there such as  in the Axe releases thread. Normally we lock topics if the discussion goes off topic, there is excessive trolling, or there is a heated debate going on.

oh thanks! hah and yeah i did read Hot_Dog's z80 ASM for the Absolute Beginner, but stop at chapter 13 because it got kinda complicated. When i first read it was easy, but then it got little confusing and hard to understand later

That's one of the things with z80 asm I've noticed. At first it is really easy to get into, if not the easiest asm language for beginners. But then when you get into the more advanced topics such as the index registers and the other complex instructions you can get lost. One of the hardest things with z80 is writing perfectly optimized  code because there are often many unique solutions you can take to solving a problem.

Back when the Prizm came out I learned Super H asm and at first I was a little lost with the lack of z80 style literals and the addition of bit shifted displacements and a pipeline architecture. But once you understand the organization of the memory and how to properly use displacements and data tables, it becomes really easy to learn the advanced concepts, especially optimizations. For example in z80 if you want to load 0 into a then you would write xor a instead of ld a,0 because it is faster. In Super H you could do either one, but I prefer MOV 0,R0 instead of XOR R0,R0 beacue they are both 1 clock cycle and MOV is easier to read.

Great to see that you've had much time to work on this. I'e been very limited lately and will be this weekend because I have an AP exam on Tuesday, but after that I will be practically homework free for the rest of the school year.

And because you are planning to use JIT compilation later on, one thing that I found that can increase speed there is when writing the routines into the runtime ram, you write them in at a fixed length that way jump statements don't require intervention on the work of the interpreter. What I'm setting up for the 84+ emulator is that originally each routine when written to ram would be extended to 64 bytes, but this proved to be too short so I'm increasing it to 128 bytes unless I size optimize the routines at the cost of speed. This would then allow execution to then jump around quickly if for example a for loop was written in the runtime ram. This would be especially useful for java because there is no worry about SMC unlike the 84+ and a less complex memory manager would be required.

I don't think TI will necessarily remove Lua, but they might make it incompatible with user made programs and only allow TI made Lua programs. The other possibility is that they might restrict Lua to something like less graphics operations and/or slower speed. And I'm really starting to wonder now, if we all hate TI so much then why do we buy their calcs. I've been loyal to them on the 84 side, but all of this nspire and CX stuff just makes me mad.

Knowing TI they will claim that is was us messing with the boot sector and not their own bugs that caused the bricked calcs to occur. Remember that TI Doesn't Care

Don't worry about threading the interpreter now. The most important thing is to get the basic runtime up and to ensure that it works. Then we can add the more complex features such as garbage collecting, threading, and Just in Time Compilation. Also unless you already have it working don't bother with the floats right now because we have some more important work to do.