Basic+

[bfr]

http://dragonfire.unitedti.org/asmin28/ref/z80is.html

Look where it says "opcode." If the opcode is formed of one 8-bit part (such as 11101011 for ex de,hl), then the instruction takes up one byte. If the opcode is formed of two 8-bit parts for a total of 16 bits (such as 11101101 : 10101000 for lddr), then the instruction takes up two bytes, etc.

There's a probably a better way to find out how many bytes each instruction takes up, as DarkerLine, bananaman or somebody who knows more about Z80 assembly will probably point out.

[Rebma Boss]

**********************************************
A new poll is up for two days! Please visit this link,
Poll Instructions, before voting.
**********************************************




Actually, that works perfectly! I have this file, but I didn't notice that the opcodes were the numbers that the calculator uses for instructions. Thanks!

[cjgone]

More organized chart:


open with note pad or else its hard to read

[AaroneusTheGreat]

Using an opcode table. You could make a table with two fields, one opcodes and one byte values, and then use a simple script to read through source code, cross reference the opcodes from the source with the table, and then increment a size variable with the value you got from the table. And use that where you need to.

It'd take some time to make though.

[Rebma Boss]

Great idea--that's actually what I was thinking about. As for speed, I'm sure that people won't care, but I don't plan to make translation time long--maybe one minute for a GIANT program and two seconds for a small program.

[bananaman]

I'm glad to see you working on this project. If you succeed in producing optimized code I may just start programming stuff for the calculator again. My only complain against assembly language programming is the vast amount of time it takes to write anything substantial b/c you personally have to write tons of code that higher level programming languages don't require. QBasic was actually the first language that I learned about 10 yrs. ago so maybe I can still remember some of it. I haven't touched it since elementary school, but I bet it won't take too long to get reacquainted with.

[Art_of_camelot]

This looks like a very interesting project, and I can't wait to see where it goes. I did dabble with q-basic a bit back in the day and it is fairly easy to work with. Keep it up, I can't wait to see more progress.

[Pseudoprogrammer]

Eh, even if it ends up making programs the size and speed of BASIC, I will still use it to access things you can't in BASIC.

[Rebma Boss]

True, you can use Basic+ to access things you can't in Basic, but SLIDE (I'll describe it in a moment) can do the same thing. Basic+ is meant to match ASM for speed and size, especially with help. (That's right, be sure to check example programs--the first one, coming soon, will clear the screen, and draw a line left, right, up, or down depending on key input. It will also quit depending on key input. If you have suggestions, these are a great place to start.)

So what is SLIDE? Check out this website! SLIDE

If you don't care about processor-intensive programs, but want easy-programming ASM-access features, SLIDE is the way to go. It's easier than assembly, and almost as fast. (It's also a great thing to use while waiting for Basic+)

SLIDE is meant to be almost as fast as ASM. Basic+ is meant to be easier and to give almost flawless, if not entirely flawless, ASM code--in other words, it is meant for processor-intensive programs.

By the way, expect a progress update tomorrow. I had to spend time deciding what to do about key input.

[JoostinOnline]

[Rebma Boss]

PROGRESS SO FAR

From now on, I will be posting my progress as text files. This way, I can say how much of something has been done, as well as what has been done. I will still post "Next on my to-do list" as replies.


NEXT ON MY TO-DO LIST:

1. Finish Chapter 1 Documentation
2. Add commands for drawing lines
3. Write Test Program #1

Priorities come first, but I hope to have Test Program #1 up by Saturday. Keep on the lookout!

[Rebma Boss]

I'm sorry, I forgot to post my progress text file. Here it is! Be sure to view it in a maximized window, because it's in a table format.

[Rebma Boss]

Well, I promised to post every week, but I've been very busy, so not much progress yet. What I'm currently working on right now is a sub for parenthesis, so that I can translate the arguments between them. All week, I've been having issues with it, and I realized that the problem is I need to rewrite the whole sub. So, that's my next step.

[WikiGuru]

i'm sorry . I run into that problem a lot, too (re-writing large chunks of code). It's the main reason why I usually drop projects (please don't drop this, it has so much potential to be great!)

[Rebma Boss]

I don't have an option that allows me to "Add Poll", I have only "New Poll." Can someone in charge allow me to add a poll to this topic so that I don't have to create a new one?

Anyways, here's something for everyone to think about, and that's where the poll is concerned. It might be easier for everybody if I translate TI-Basic code (instead of QuickBasic code) into ASM, the difference being that there would be several new subprograms (similar to Ti-Basic commands) that would include ASM functions, unlike previous Ti-Basic to ASM translators. Once again, the translation would make the program as fast, or almost as fast as, ASM, and QuickBasic would still be needed to debug and write programs.

Here are the pros and cons:

Pros

1. Hopefully everybody knows TI-Basic! It will be easier for everyone to work with, and easier for me to translate.
2. The documentation will be easier to follow. Instead of teaching a new language (QuickBasic), the documentation will simply teach what a Ti-Basic programmer needs to know whats new, therefore it will be easier to follow and quicker to read.
3. New Ti-Basic functions will be added so that a Ti-Basic programmer can use ASM-type commands.

Cons

1. Basic+ will take a little bit longer because I have to rewrite some of the code
2. QuickBasic will still be needed--Basic+ Ti-Basic programs cannot be written or debugged on a calculator

So, that's what the poll will be. Once again, could someone on this site make it so I can put the poll on this forum? Thanks!

[Weregoose]

Poll added! Please read the above pros and cons before voting.

[Rebma Boss]

For everyone's informaton, Basic+ will be on hold for two days. I need people's votes as to whether to translate Ti-Basic code into ASM, or QBasic code into ASM.

This is the only poll that I will take for only two days. Why so short? I can't continue Basic+ until I know for sure what everybody wants. The reason is hard to explain.

So, please voice your opinion, I will continue work on Basic+ after Monday the 21st, which is when the poll will end.

Just a review of the poll instructions:

[Rebma Boss]

Just a reminder that today until midnight is the last day for the poll. After that, I will continue work on Basic+.

But there's a change--I listed in the cons that Ti-Basic programs involving Basic+ could not be written or debugged on the calculator, but with the help of Xlib and Celtic III, I think I can actually implement this feature.

So there's another pro--even though QuickBasic programs require QuickBasic, Ti-Basic+ programs (with the additional subs to give them "ASM" features) can be written on the calculator.

REMEMBER: Just because Basic+ would convert Ti-Basic code if chosen, that doesn't mean that only Ti-Basic code will be converted. There will be pre-written calculator subs that allow ASM functions (such as AppVar writing, Sprites, etc.) that Basic+ will convert.

[WikiGuru]

I'd say no to TI-Basic because that really will actually hinder someone's ability to program z80, and it might lead to a mis-match of sorts where a person would start programming q-basic like z80 and somehow mix in TI-basic. It'd be hard to translate and confusing to a programmer because of the mixing of two very different syntax's.

[Rebma Boss]