And to follow up on Zachery - I agree. I always thought of MOSA being more
about standards and less about code. A MOSA compiler is a great idea - and
it will probably involve some standard libs that a MOSA kernel might need to
tap into (to use, for example, the "Intrinsic" attribute that grover
exampled earlier) to use the compiler.
And maybe, down the road, we can agree in enough commonalities for a HAL and
a JIT (well, of course the JIT, if we all end up using a common compiler),
that we will have more interfaces that we will either need to implement or
code against. (But no standard implementations.)
I think though, for now, the MOSA compiler having some sort of simple kernel
with it, is making the compiler easier to develop. I believe it was grover
that pointed out that because of the way SharpOS expects to be AOTed, the
MOSA compiler can't really handle us yet.
-------------------------------------------------------------------------
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
