Earl's Coconut Palm Page

I’m back to working on my ml Urbane. I keep going back and rewriting what I have done so I don’t get very far. Oh well.

I was using urbane for the disk io in my machine language editor, and I decided that it was overkill, so i wrote light (light urbane). Labels are all lower case, have to end lines, and variable names stay the same. That way you can have meaningful variable names that don’t change. Usage is light file. You can add lines drop lines and move lines, run it through light and the line numbers are all fixed. You can also use light in out, but I found that I never used it that way. Light.zip

I’m writing an editor in machinge language for Urbane in machine language.
I wanted to use urbane for the decb portion of the program to work with
the disk portion of the program. My copy of urbane wouldn’t work so I
figured that it just got corrupted. So I went back to the forum to get the
original version, and discovered much to my dismay that the distribution
didn’t include an executable. Not to be daunted I downloaded MinGW and the
source and compiled it again. Bonkers. It still didn’t work. With a little
work i managed to figure out that the problem was carriage return line
separators instead of line feeds. So I rewrote urbane to handle carriage
returns, line feeds, and even carriage return line feed pairs for good
measure. While I was about it I cleaned up the code. Got rid of most of
extra files, and made it ansi compliant. I even cleaned up the parameters.
urbane infile -o=outfle -v -l -l=listfile -e=errorfile -x=xref. No
parameters lists the parameters. I even included an executable. urbaneBD.zip

I’ve got a fair editor so far, but I think I will proceed with my assembler before tackling Urbane Basic. That way I can use the assembler system on Urbane and check the assembler out. I think that I will work with 6309, and increase the buffer size to 380k. Big plans Ha Ha

I’m writing it in m6809 assembly language. At present I have a simple start for a linked list editor. As I see it my system will have a 60k linked list partially compiled Urbane Basic file. That will free up 30k for low level graphics and data along with the 32k for super high level graphics. If I get that done I might jump into Toolshed.

I am going to try to get rid of the middle compile phase and have a program that translates an urbane program directly into an executable.

a new one Oops, I forgot to get rid of some debug lines one more try

I have a working version of my small subset of coco urbane basic to c program. here it is here is a slightly improved one and another one before I get rid of the middle compile phase and make it just an urbane to executable program.

Super Disk Extended Color Basic compiled and/or c language. The final result will be SDECB functionality for nitros9 c. In addition to the c compiler that I mentioned in the last post, I am working on a c program to translate a small subset of urbane basic to c source.

My latest efforts lie in creating c functions for EC Basic in a strictly limited subset of c. I want to make it be possible to write itself in itself. I am presently writing a lexical analyzer on the PC. The next step will be to write a cross-parser between the PC and the coco. Then comes an interpreter for the coco. At that point I may want to add a cross-compiler and/or a coco compiler.