On Nov 16, 2007 1:16 AM, Bruce Markham <[EMAIL PROTECTED]> wrote:
> It doesn't show Microsoft's implementation code, it doesn't talk about
> specific algorithms. Just basic data layouts. The text is copyright, but
> there is no further notice about intellectual property.
>
> In fact, if it were material of a sensitive nature, it wouldn't be
> published in MSDN Magazine. And it would likely be covered by an NDA, if you
> were lucky enough to get to see it.
>
> I understand the fear - but honestly - if Microsoft is so evil, I'm sure
> they would just invoke something in Visual Studio licensing to shut down the
> contributors who used Visual Studio to help make this happen.
>
> On Nov 15, 2007 11:49 PM, Dennis Hayes <[EMAIL PROTECTED]> wrote:
>
> > Is there concerns here about being "contaminated" with MS IP and then
> > contributing to SOS?
> > The mono pholisopy is you can't contribute after reading MS source or
> > decompiled code, but public docs are generaly OK, not sure if something this
> > detailed would be a problem with Mono or not.
> > I would love to read this, but won't. Well I think I will post to the
> > Mono list for an offical opion.
> > Dennis
> >
> >
> > *Jonathan Chayce Dickinson < [EMAIL PROTECTED]>* wrote:
> >
> > Cor blimey!!! That is freaken awesome!!!
> >
> > Jonathan Chayce Dickinson
> >
> > * From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > *On Behalf Of *Bruce Markham
> > *Sent:* 15 November 2007 10:33 AM
> > *To:* SharpOS Developers
> > *Subject:* [SharpOS Developers] JIT what we need to do...
> >
> > I've added the link to the wiki, but it was so cool I just had to share
> > it anyway...
> >
> > http://msdn.microsoft.com/msdnmag/issues/05/05/JITCompiler/
> >
> > A nice article, from 2 years ago, talking in detail about how .NET 1.1JITs,
> > what its vtables look like, and how its various heaps line up.
> > Straight from the horses mouth.
> >
> > Thought it might be useful...
> >
> > Well, at least Miguel didn't think it was contaminating. But at least
Dennis is still lurking and looking out for our future! ;-)
I'm still trying to wrap my head around this stuff. There's what little we
know about MS .NET. There is Rotor. There is Mono. Its hard, because the
safest of things to look at, is the most cluttered.
But I think the link I posted is probably the only safe shot we have at
getting an abstract feel for how MS does it. Not that I think it is how we
should do it, but at least it gives us some ground to push off from.
Does anyone else have any legal, or design and implementation, thoughts to
share? We need to start tackling this folks.
-------------------------------------------------------------------------
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
