Posted: Fri 24 Nov, 2006 5:19 pm
So you want an awfull lot of them, for every command 1? If you're making your own editor you could just use a large LUT and replace every byte by a string..
Page 2 of 2
Posted: Fri 24 Nov, 2006 10:51 pm
Not for every command, but for every instruction and flag and some other ti83plus.inc equates. I think registers would also have a token associated with it, and the combination of an instruction, register, or a memory destination would be replaced with the appropriate hex or binary code.
Posted: Fri 24 Nov, 2006 11:27 pm
Sounds like a very good idea, but I fear there will be some limitation keeping you from using that much tokens 
Posted: Fri 24 Nov, 2006 11:46 pm
Well, I still don't know how to go about making tokens, much less know about what limitations will keep me away from making that many.Timendus wrote:Sounds like a very good idea, but I fear there will be some limitation keeping you from using that much tokens
Posted: Sun 26 Nov, 2006 10:39 am
If you're only going to use the tokens in your own editor, you could just do something like this:
there should be a mistake/typo in it somewhere, never trust my code 
and the code at Text should look like this:
And if you're going to use the old program editor, well, I'll look into it (I'm using it, but I use lowercase letter-tokens)
Code: Select all
;hl is pointer to the place you store the stuff
ld l,(hl)
ld h,0
add hl,hl
add hl,hl
add hl,hl ;8 times HL, assuming you use 7 letters max
ld de,Text
add hl,de ;hl is now a real pointer to the text
bcall(_PutS)
ret ;if you're making this a subroutineand the code at Text should look like this:
Code: Select all
Text:
.db "add ",0,0,0,0
.db "adc ",0,0,0,0
.db "bcall(_",0
etc.. etc..Posted: Sun 26 Nov, 2006 1:37 pm
Yeah, that's what I meant, although I feel it needs to be more dynamic for editing and parsing. I like the idea for a base code which I will try to expand around.
Posted: Sun 26 Nov, 2006 8:34 pm
Ok, good luck