Quote from: kindermoumoute on October 13, 2010, 04:47:54 pm

I do not know if it's already been asked, but it would be nice to compile a program Axe Parser in ASM/Ion TI-83 (from the calculator or computer).
Is it possible?

I've been thinking of writing a program to do this, I'll get back to you on it later.

That might be cool, as there are still 82 STATS/83 users (both the same calc) around in Europe.

is there a way you could let getKey() take a variable as an argument? so getKey(A) would be valid. it'd help if you wanted to let the user configure his controls.

is there a way you could let getKey() take a variable as an argument? so getKey(A) would be valid. it'd help if you wanted to let the user configure his controls.

I guess such a routine could exist, but because of how the keyboard hardware works, it would be fairly bulky and slow. It's probably better to just stick with preassigned keys.

---

EDIT: So as not to double post, I'll add the following as an edit. It is, however, entirely unrelated.

I guess this request is sort of a form of look-ahead parsing, which is generally difficult to implement, but I believe this is a very basic form that has already been similarly implemented with pre-calculation involving constants. I was wondering if statements such as A+{L₁+4}^r, which is currently parsed as:
ld hl,(A)
push hl
ld hl,(L?+4)
pop de
add hl,deCould be optimized to be like normal variable addition:
ld hl,(A)
ld de,(L?+4)
add hl,deThe same goes for things like subtraction and any other things I may be forgetting that could be optimized this way.


EDIT 2: Oh, by the way, you misspelled "routines" in the fourth line of the Commands.inc file

---

EDIT 3: Man, this post is getting really big! But I promise this next feature request will be simple, I'll even give you the code for it!

p_DispHex:
.db __DispHexEnd-$-1
ld c,h
call __DispHexByte
ld c,l
__DispHexByte:
ld a,c
rra
rra
rra
rra
call __DispHexNib
ld a,c
__DispHexNib:
or F0h
daa
add a,A0h
adc a,40h
B_CALL(_PutC)
ret
__DispHexEnd:

p_TextHex:
.db __TextHexEnd-$-1
ld c,h
call __TextHexByte
ld c,l
__TextHexByte:
ld a,c
rra
rra
rra
rra
call __TextHexNib
ld a,c
__TextHexNib:
or F0h
daa
add a,A0h
adc a,40h
B_CALL(_VPutMap)
ret
__TextHexEnd:

---

EDIT 4: Oh, and you haven't forgotten about this, have you? Haha sorry for swamping you.

Mabe you could make it so you can insert program icons. (Like in Doors or Mirage.)

.PROGRAM Description
.[16*16 hex icon]
[i]program code[/i]


If you urgently need a routine for that, you could do it with the following assembly:

Code: [Select]

Asm(AF474FEDB921FFFFED42)Just put the pointer value right before that.

That's actually exactly what I'm doing right now (even the hex string, I'm pretty sure). I just thought it might be a feature that someone might need in the future, and length( doesn't take an ^r yet anyway.

Setting the rand seed (think K->rand in BASIC).

(Also, on another rand note, when I use the included Guess the Number program from Mirage, the number is always either 4 or 6. Another reason for this command.)

I think it's {L1-2}^r, the two bytes after A-Z and theta vars.

Mhmm interesting. Personally for a game I would kinda be relunctant about setting the seed, though, because then people can memorize random number patterns and abuse luck manipulation in games