OpenEuphoria

Re: EuOS

• Posted by Jeffrey Fielding <JJProg at CYBERBURY.NET> Sep 23, 1998
• 553 views

For running such a project, there has got to be a web site. It should have
a list of the people on the team, the current status of the project, how to
sign up, and other things related to the operating system.

There should also be a mailing list. I think you can create a mailing list
by going to www.makelist.com.

Since operating systems are usually very complex, and there are many people
working on them, there needs to be a way to organize the operating system,
and some standards that should apply to most (and hopefully all) of the
operating system. I suggest:
* Every procedure, function, variable, constant, type, and file should be
documented giving a description of what it is used for, the format that it
is in, the person who write it, and all revisions.
* Every change to the code should be documented, for example:
-- BUG FIX: Used to return 0 when it should have returned 1
function uselessFunc()
        return 1 -- Used to be: return 0
end function
* Everyone's ideas should be posted on the mailing list, and on the web
site. Before anyone starts programming anything, everyone should agree on
what format it should be in, who should write it, and exactly what it
should do. This should help prevent mistakes like:
function uselsessFunc(integer a, sequence b)
        return 1
end function
? uselessFunc({1,2,3},90)
* There should be a standard interface for everything, and it should be
followed as strictly as possible. Everything that can go wrong should be
checked for, and a unique error code should be returned. All codes should
be defined as constants.
* The web site should have a database of all the functions, procedures,
types, files, variables, and constants. It should also show revisions,
comments, and documentation. I could write a Java applet to keep track of
this, I think.
* The web site should have a list of what is being worked on and by whom,
and what needs to be written, so that people can pick something to work on.
To make things efficient, check back with the web page frequently and post
your status and any problems you have coding.
* Try to comment your code so that people can understand it, and you can
understand it when it gets to be really long.
* There could be a development environment that gets information from the
Internet and posts new code and suggestions.

Jeffrey Fielding
JJProg at cyberbury.net