lol yeah, much of my coding gets done during chem.

Yeah, I remember RealSnd making those HUGE apps...I think a 1 minute Pokemon theme song took just as much space as the pokemon TiBoy app
But midi would be awesome..

Adv Wars //one of my fav handheld games ever, especially Dual Strike, rivaled only by Pokemon and Zelda
Knight OS  // 3rd party OS w/ multitasking, etc.? Win
HL2 // Like DJ, I'm not that into the low lvl stuff, especially since Axe came out (I was just about to start learning ASM when it came out, so then I was like......this looks more interesting)
tiDE / Mosaic tie for last: as I said, I don't do z80 or any kind of coding on the comp...so I can't really have a preference for either of them

Yeah, i guess reporting a bug isn't very helpful w/o the source , but, as you guessed, it's a contest entry. However, I think I've figured out what causes it: using the Mirage interrupts, like On+Mode to quit to the homescreen. The program itself didn't seem to cause this bug every time I ran it; it occurred to me that the glitchy lists appeared when I would exit the program with On+Mode

well probs b/c the calc doesn't know errors, and instead is like KTHX SOMETIN ^0= INFINITY and then says goshdarngolly we can only process 65535. kind of like how in pokemon red having a lvl 1 mew gain less than 54 xp lvls it to 100 (because at lvl 1, it has -54 xp, but it's not really 54, it's like 2^64-54 or something) so the processor assumes it has enough xp for lvl 255 and forces it to 100</offtopic>

anyway, after compiling and running an axe prog, i was scrolling through my mem menu, when all of a sudden an ERR: MEMORY popped up. upon hitting 2:Goto, it showed the mem menu and L2, but w/o a size for L2 or the little arrow cursor. Upon using the STAT editor to look at L2's contents.... (see screenie)

looks nice
you're right, though, the speed is painful
also, i would suggest not clearing the homescreen after a unit conversion, and not having parentheses for prefixes (though i don't know how possible that is)
I like how you also included Google's little "answer to life/universe/everything)

edit: do you think you need parentheses at all? i can't really see why they need to be there for clarity ( i mean, (7 (in))=17.78((c)m))) is kind of silly
and i can't think of why they'd be needed for coding purposes...although i may be wrong about that

edit2 didnt read your whole first post. so, parentheses ARE needed...damn

edit3 lol i'm a little "submit button" happy today...what if you ran another routine that's kind of like a "find and delete" to kill parentheses? although it might make the program even slower...and also tightening the user's syntax to allow for spaces to be cushions over parentheses might be viable...

Also, it's a pain that variables can't be stored in-program... although the only way for that to be allowed would be with ASM..sigh..guess you can't have everything

@DeepThought

Yeah, that's actually happened to me several times throughout my calc's history (even before Axe), but I've never romdumped it (nemo) It's been occurring a lot recently though. Once I remember (before 2.53MP, when Omnicalc still worked) I was playing around with the outrageoulsy-sized graphing vars recreating them after each crash with RestoreMem( and once i actually managed to delete it once. Mine were around 128k in size O.o and so then I had around 152k RAM. It was cool for all of about 5 seconds when the calc crashed again lol

Another bug I found with Axe is that once (again, I don't have the source, sorry) after running a compiled program, after exiting MOS (with the On+Mode interrupt, maybe this is an issue?) my cursor in the homescreen, instead of being in the normal position, was 2 rows down and 2 characters across, and it was blinking over the 3x3pixel box character. I wasn't able to type any numbers/letters etc, and upon going into the mem menu to clear RAM, once I hit "Enter" on Mem Mgmt/Delete, the calc acted like I had quit the menu: the cursor (and the 3x3 box char) reappeared, only the menu didn't go away. So i had a blinking cursor in the middle of a menu~ Eventually I had to pull a battery, which cleared the RAM. After compiling and running the exact same file, the bug did not reappear

Ok...  because of my unfamiliarity with Axe's system of numbers I decided to try in BASIC first; I managed to make it work but not in axe: it produces a bunch of random vertical lines

BASIC version
:ClrDraw
:0->Xmin
:0->Ymin
:94->Xmax
:62-.Ymax
:8->V
:5->G
:0->A
:40->L2(1
:For(X,1,94
:L2(x)-2GA/V^2->L2(x+1)
:A+1->A
:If 2<abs(-2GA/V^2
:Then
:-G+randInt(-2,2->G
:-9->A
;End
:End
;For(A,1,94
:Line(A,L2(A),A+1,L2(A+1)
:End
And then I changed it to match Axe syntax:
:.AMAP
:ClrDraw
:8->V
:5->G
:0->A
:deltaList(40)->GDB1
:For(X,1,94
:-2*G*A//V//V+{X+GDB1}->{GDB1+X+1
:A+1->A
:If 2<abs(-2*G*A//V//V
:-G->G
:-9->A
;End
:End
:For(A,0,94
:Line(A,{GDB1+A},A+1,{GDB1+A+1
:End
;DispGraph
;Repeat getKey
:End
The basic idea is to just change the Y value by the derivative of the equ gx^2/v^2 + y where g= grav. constant, v=intitial velocity, and y= initial height and flip the gravity when f'x>2