maybe name it "NikkyCE"

Congratulations on being the first to reach this important milestone, and for kicking my backside into action on Doors CE. I know this will be really bad for my upcoming paper deadline and my sleep schedule. I have a few comments and questions:
1) Why not maintain the same BASIC header format as Doors C[S]E? Having a single BASIC header format would appear to be the best option to avoid having to already have a ridiculous variety of headers we each need to support.

2) One of the problems I've been trying to solve is bootstrapping the shell's first run. Do you use a BASIC program to do so, and then let the shell handle its own execution in the future?

3) I still want to work together; I wish we could meet on some common ground on working on Doors CE together.

Bug report:
Scrolling is very slow, changing TIOS time makes it slower.

Feature request: a standard argv mechanism (preferably for BASIC too, but definitely for C/Asm)

The function called at program startup is named main. The implementation declares no prototype for this function. It shall be defined with a return type of int and with no parameters:

int main(void) { /* ... */ }

or with two parameters (referred to here as argc and argv, though any names may be used, as they are local to the function in which they are declared):

int main(int argc, char *argv[]) { /* ... */ }

or equivalent; or in some other implementation-defined manner.

If they are declared, the parameters to the main function shall obey the following constraints:

The value of argc shall be nonnegative.

argv[argc] shall be a null pointer.

If the value of argc is greater than zero, the array members argv[0] through argv[argc-1] inclusive shall contain pointers to strings, which are given implementation-defined values by the host environment prior to program startup. The intent is to supply to the program information determined prior to program startup from elsewhere in the hosted environment. If the host environment is not capable of supplying strings with letters in both uppercase and lowercase, the implementation shall ensure that the strings are received in lowercase.

If the value of argc is greater than zero, the string pointed to by argv[0] represents the program name; argv[0][0] shall be the null character if the program name is not available from the host environment. If the value of argc is greater than one, the strings pointed to by argv[1] through argv[argc-1] represent the program parameters.

The parameters argc and argv and the strings pointed to by the argv array shall be modifiable by the program, and retain their last-stored values between program startup and program termination.

Your standard entry point for programs should be akin to:

Code:


This allows for reasonable terminal interfaces, file opening mechanisms, and all sorts of goodies, for the same reasons it's a standard everywhere else.

Please keep the int return as well (though of course feel free to disregard its value in your shell). You should feel free to pass argc=0 and argv=null, or just argc=1, argv={"prgmNAME"}, so long as you are supporting the standardized entry point.

Bug report: Does not like basic programs to use Stop command: it will reset ram. I found out the hard way