er, shouldnt they use the same argument? In xLIB, OR/XOR/AND/Overwrite all use the same argument.

Yes that's correct, but it doesn't have to be that way.  The person who did xlib just chose to do it that way.  I'm working with compatability for previous Ti-Basic programs

Ah ok. What would be the advantage of separating them? I am curious about what special tricks we could do. Also is it easier to keep them separated?

To answer your question, if they are kept seperated, a person can take a Ti-Basic program, and he can easily convert it to Correlation simply by replacing Output( with ln( and Text( with e^(.  He does not need to scroll to the end of each line to add a parameter.  (This really frustrated me in Ti-Basic programming)  Furthermore, it saves two bytes per line, and I figured most of the time people are going to use overwrite except for sprites.
 
It's just as easy to keep the argument count seperate as it is to incorporate them all together.  It's just like Ti-Basic Line(, where a zero is added only draw a white line.

As a side note, if XOR/OR/AND is successful, I'll add Mask as well.  A character to be drawn as a Masked character will require 2 characters worth of data in the font, but it will be faster than using XOR/OR/AND to manually draw the mask.

Ah ok so you wanted default method to not require arguments? What about the other? Will it default to OR? I still don't get why you keep them separate.

ln(1,1,"AAAA") will display "homescreen" text AAAA using Overwrite.  e^(1,1,"AAAA") will display small text using Overwrite.

ln(1,1,"AAAA", 1-4) will display "homescreen" text using OR, AND, XOR, Mask.  e^(1,1,"AAAA", 1-4) will display small text using OR, AND, XOR, Mask.

I'm afraid I can't explain any better why I keep them seperate.  Just remember, Line(1,1,2,2) displays a black line, but if you add an extra argument--Line(1,1,2,2,0)--you get a white line.

Ah ok so basically it's just that if no argument is specified, it uses Overwrite? I was confused since with Line if you add a 5th argument that is a 1 it's the alternate way to display a black line (probably for those who don't use a constant for it and want to create a flashing effect)

Will the homescreen text be confined to the 16x8 grid, or will the location be like with Text(?

After two weeks of head throbbing from having to do only what the OS let me do, I'm getting close to a screenshot release.  I just have some bugs to fix in the ln( routine, but the parser is working so far.

Here's a new screenshot: A first look at Output using ln(

Note that the run indicator won't be there in the future, but I had to pause the program to test it.

The program is only 10% done, but this is definitely the end of the step 2.

Wow!  thats looks great!  are there any known bugs?

There are so many bugs that if they were all fixed, the program would be 20% done.  Basically, I can't list them all. 

However, I will say that there's a "Syntax Error" from the parser after the ln( statement is done executing.  Something I can fix, but need to do.  Also, the routine doesn't yet clip sprites, and ln( doesn't correctly display in a 16 x 8 grid yet.