sounds cool!  btw, is Deep Thought on the team?

So, I didn't see this on UTI.  What exactly is it?

right here:  http://www.unitedti.org/forum/index.php?showtopic=9492
sounds pretty cool, maybe this could be integrated into KOS along with some of Axe?  just a thought. 

i noticed a small problem concerning memory. you said that variables have a shaddow variable that has 27+ status reads available, which i think is really cool. but that makes each variable 27+ bytes large. i dont mean to be offensive, but after each operation with the variable, wouldn't each of the 27 status' have to be updated, creating a big slowdown? also, what operator is the "." operator? i saw the line "deout.X.Y."Hello, World!": k.wait" is deout a reference to a system object? i do recognize the similarity to cout in C though. also, is k a reference to another system object, telling the program to pause? i can't wait to see progress on this

i noticed a small problem concerning memory. you said that variables have a shaddow variable that has 27+ status reads available, which i think is really cool. but that makes each variable 27+ bytes large. i dont mean to be offensive, but after each operation with the variable, wouldn't each of the 27 status' have to be updated, creating a big slowdown? also, what operator is the "." operator? i saw the line "deout.X.Y."Hello, World!": k.wait" is deout a reference to a system object? i do recognize the similarity to cout in C though. also, is k a reference to another system object, telling the program to pause? i can't wait to see progress on this

The status reads are only 2 bytes large.  but, there are 27 different functions to attain these statuses.  Like, let's say you want the status 'Pointer'.  It would return the pointer in the 2 byte status.  Or if you wanted size, or length, or amount of occurences of a number starting at the variable, it would return those in the status.

I was also thinking that KOS would be a great platform for this but so far sircmpwn isn't showing any interest in having it on KOS

@Nemo: That was the old syntax, I was starting to change it before I stopped working on it on UTI.

well, I guess we can work out some details until then

Well, sir, one question:

It looks like KOS handles multitasking and such, which is cool, could definately be implemented in threads on 'DE.  But how much memory is available to programmers?