ungroup it on the PC side and then send it, your calc might be screwing up the ungroup
New bug fixed: Equates are no longer assumed to be 16-bit.
And I need YOU, the user, to tell me what I should fix, because otherwise, this compiler ain't gettin' nowhere fast.
And I need YOU, the user, to tell me what I should fix, because otherwise, this compiler ain't gettin' nowhere fast.
*bump*
Yes! Fixed it! And the solution was much simpler than I thought it would be...
Solution: When it comes across a label, it checks to see if the label is anywhere in the include string. If it is, it adds the label to the beginning of the include string; otherwise, it adds it to the end.
Fallen Ghost wrote:
Ok, I managed to do a simple gui program (just for fun in some math class). And I noticed something. It gave me an Error: Label when I had
jr z,MUP
jr LOOP
MUP:
cp 4
jr nz,MUPN
ld a,8
MUPN:
ld (CURROW),a
Your compilator gave me that error when parsing jr z,MUP, second part, so the MUP label. After changing and playing with the labels, I found that when you had a label name and another label name that both have the same start and that one is smaller than the other, it bugs.
Would bug:
[DRT,DRTVG]
[AVK,AVK3]
[BJH3,BJH]
Would not bug:
[DRT1,DRTVG]
[AVK2,AVK3]
[3BJH,BJH]
jr z,MUP
jr LOOP
MUP:
cp 4
jr nz,MUPN
ld a,8
MUPN:
ld (CURROW),a
Your compilator gave me that error when parsing jr z,MUP, second part, so the MUP label. After changing and playing with the labels, I found that when you had a label name and another label name that both have the same start and that one is smaller than the other, it bugs.
Would bug:
[DRT,DRTVG]
[AVK,AVK3]
[BJH3,BJH]
Would not bug:
[DRT1,DRTVG]
[AVK2,AVK3]
[3BJH,BJH]
Yes! Fixed it! And the solution was much simpler than I thought it would be...
Solution: When it comes across a label, it checks to see if the label is anywhere in the include string. If it is, it adds the label to the beginning of the include string; otherwise, it adds it to the end.
KermMartian wrote:
You need to make single quotes work for character constants, eg. asciization of 'a', '4', '_', etc.
Hey! That was my idea from sax
Any fool can use a computer. Many do.
Harq wrote:
KermMartian wrote:
You need to make single quotes work for character constants, eg. asciization of 'a', '4', '_', etc.
Hey! That was my idea from sax
Added support for single characters inside single quotes and improved the "smart label" routine.
Edit: Actually, I changed it to double quotes because otherwise all special chars and lowercase letters would get messed up.
Edit: Actually, I changed it to double quotes because otherwise all special chars and lowercase letters would get messed up.
Keep up the good work. I may eventually use it for an oncalc TICI 2.0 CSA driver - I want to play with my color screen a bit.`
KermMartian wrote:
Keep up the good work. I may eventually use it for an oncalc TICI 2.0 CSA driver - I want to play with my color screen a bit.`
wait wait wait...
color screen...
Come again?
Any fool can use a computer. Many do.
Harq wrote:
KermMartian wrote:
Keep up the good work. I may eventually use it for an oncalc TICI 2.0 CSA driver - I want to play with my color screen a bit.`
wait wait wait...
color screen...
Come again?
http://www.ticalc.org/archives/files/fileinfo/269/26943.html
Keep in mind it's changed a lot since I released that. If I can find a camera, I can show you what I have so far.
Okay, I have good news and bad news.
The bad news:
My calc reset and Omnicalc's backup image was from about a week ago, so I lost all my progress on the compiler.
The good news:
I was able to recreate all of the new features, and I added support for negative decimals (long overdue). I also changed the name to OTBP Assembler 1.
I think this topic may need to be moved to Announce Your Projects, btw.
The bad news:
My calc reset and Omnicalc's backup image was from about a week ago, so I lost all my progress on the compiler.
The good news:
I was able to recreate all of the new features, and I added support for negative decimals (long overdue). I also changed the name to OTBP Assembler 1.
I think this topic may need to be moved to Announce Your Projects, btw.
I just made yet another asm subroutine, perhaps the most useful for an assembler. It finds the "value" of a string and returns it in hex. For example, you can now do
Code:
Overall, it saved over 400 bytes!
Code:
:ld a,progobj+01010101b-5+"a"+34hOverall, it saved over 400 bytes!
No parentheses. I don't see why you'd need them. What it does first is start parsing as if it's decimal, but if it finds a character that's not 0-9, it parses as if it's hex, if error, it tries binary, if error, it tries searching through Str9, if error, the returned string is "ERR."
Why not search for an EOL or plus or minus, then look before it and see if you have a b, h, or d? Also, does it support %,$,[none] prefixes?
- 05 Jan 2007 10:21:58 pm
- Last edited by calc84maniac on 06 Jan 2007 10:10:11 am; edited 1 time in total
Register to Join the Conversation
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Advertisement