>From reading the log, and stopping by to say my own 2 cents, I gather that
the meeting was a good success!
I'm already working on a more sophisticated RuntimeCop that we will be able
to use to list method/property stubs that we need to implement, as well as
types that we need to be able to marshall between EIC and EDC.
It will hard-reference the AOT.Core, and load the currently compiled kernel
at runtime, along with mono corlib, and System, to either list stubs that
need to be implemented, need to *still* be implemented, and dump husks for
both. It will make use of an "IR" layer, (sounds fitting, right?),
Mono.Cecil, and CodeDOM to do its duty. Though a GUI might eventually be
needed to analyze dependencies, currently only a command-line utility is
planned.
This will take a few weeks to pull off, and we will only need, hopefully, to
run it a couple times (so it shouldn't need to be part of our regular build
chain), but I think it is a good step in the right direction unless anyone
has any objections.
I personally object to the idea of re-writing our own corlib and System
simply because of maintenance issues (versus just implementing the stubs),
but if we need to, we can open up discussion about it and then have the
board take a vote.
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
