> The basic goal behind SharpOS is to produce a functional operating > system using as much C# as possible and as little C/C++ as possible. > So far we've not had to make any C code, and assembler-level > programming is available via a stub class (delegated into so-called > Arch-Dependent-Code (ADC) layers).
How open are you guys to changes? I haven't reviewed it yet - it certainly seems inline with my thinking.. But if say I review it, and find things worth discussing, are we still pretty much jello or are we more solid? For my background you can check some links below, or just Google me. -- Chad Z. Hower aka Kudzu "Programming is an art form that fights back" http://www.KudzuWorld.com/ http://www.Woo-Hoo.net/ http://www.DelphiToDotNet.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ SharpOS-Developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sharpos-developers
