This is a longer discussion. The MOSA effort as it is right now is primarily the forum & svn hosted by Scott Balmos (now Ensemble). My personal intention is to make MOSA a shared effort by both SharpOS and Ensemble. The problem both projects face are those of contributors/contributions and as we have discussed more than a week ago about architecture. We have to more or less live with the split efforts, however I think we can share the code we develop.
My contributions to MOSA include: - A compiler - Beginnings of a VES with support for reflection and other things packed on top I hope we can extend this through shared efforts to include: - A common kernel - A common driver model and driver code - A common port/adaptation of monos corlib One additional goal is to make MOSA attractive for research. I have a lot of ideas in this regard and especially my vacation week was very productive to accomplish these goals. My *personal* thinking of MOSA is that it acts as the core kernel and SharpOS/Ensemble/... become distributions based on this kernel code in different configurations including/excluding certain things. I know this isn't easy for some of us and it isn't easy for Scott. However looking at the active contributor lists and the overall progress this is the only way I see both projects or either one can move forward. Either we work together or we die together. The AOT is working for us right now. I would like to keep it along as long as possible. However there's no real maintenance there as I see it. Mike > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Im > Auftrag von Sander van Rossen > Gesendet: Dienstag, 29. Juli 2008 13:36 > An: sharpos-developers@lists.sourceforge.net > Betreff: [SharpOS Developers] MOSA / AOT > > I'm looking trough the issues on the sharpos webpage: > > Is Mosa (going to be) a replacement for the AOT compiler? > I'm asking because we have several issues (also for the next > milestone) related to AOT. > If nobody's going to continue working on the AOT, and it's > going to be replaced, then those issues would never be met > and should be removed. > (for example: "AOT documentation issue" / "Support for > floating-point primitives and arithmetic issue" / "Add > support for constructors of arrays that are not 0 based.") > > > > Also, there still seems to be one open issue on exception handling.. > Anyone got any idea what the status is on that? > (same goes for "Some interrupts need to throw exceptions just > like DivideByZero" issue) > > -------------------------------------------------------------- > ----------- > This SF.Net email is sponsored by the Moblin Your Move > Developer's challenge Build the coolest Linux based > applications with Moblin SDK & win great prizes Grand prize > is a trip for two to an Open Source event anywhere in the > world http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > SharpOS-Developers mailing list > SharpOS-Developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sharpos-developers > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
