I think that was actually the idea we had, and it would eventually be replaced by code living in the OS itself when we supported reflection (or AOT can't remember?)
On Fri, Jul 25, 2008 at 5:12 PM, Bruce Markham <[EMAIL PROTECTED]> wrote: > From the last I can remember, we just don't have reflection in the kernel. > > What I think we really need, is an intermediate tool that will read the IL > of the driver stuff, read the attributes, and then create implementation > objects. With proper configuration, like having the interfaces in their own > DLL (or multiples), and then only re-"mapping" what has changed, we can keep > compile-time down. > > *shrug* Just an idea... ------------------------------------------------------------------------- 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
