On 9/18/07, Bruce <[EMAIL PROTECTED]> wrote: > other room for AOT work - floating point > Something else, that has been ignored for forever and a day, is the need for > floating point in the AOT. I looked into it once, and got completely > confused by various conflicting terminologies I found on the internet. > However, we definitely need it. (Such as, for the scheduler.)
I don't think it's a good idea to use floating point in the scheduler.. Floating point has it's uses, but it has a whole range of problems that you wouldn't have if you simply use integer math instead. And we definitely don't want to have floating point errors or floating point precision problems in the kernel ;) > Other potential side-projects, more or less useful to SharpOS at present > time: > * Drivers - anyone that wants to draft up some documentation on a potential > driver abstraction layer and architecture, start talking about it now. The > sooner we can define a model for drivers, the sooner we can start working on > them. (If you expect pretty SharpOS GUI action, this is where you need to > start...) I'm currently working on a scheduler framework and drivers would definitely be a part of this, altough i haven't gotten to this part yet. Any help with it would be appriciated. Right now i'm using some stuff that the aot doesn't support yet such as generics and (stub-)classes. These could be worked around for the time being however.. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
