Legal Implications of viewing the Windows code.

[Grifter]

I just figured I would raise the point that, with so much discussion about the leaked Windows code. If you are working on or ever plan to work on an open source project in the future. DO NOT LOOK AT THIS CODE!! And if you do, don't talk about it, not even jokingly. You give Microsoft a reason to say you have used their ideas or code itself in your future endeavors, and as we know...this is bad.

Just my $0.02

[singe]

I just figured I would raise the point that, with so much discussion about the leaked Windows code. If you are working on or ever plan to work on an open source project in the future. DO NOT LOOK AT THIS CODE!! And if you do, don't talk about it, not even jokingly. You give Microsoft a reason to say you have used their ideas or code itself in your future endeavors, and as we know...this is bad.

Just my $0.02

This raises an interesting point. While personally I couldn't care less about this chunk of code, I was wondering the same thing about SCO - by poking about in the Linux guts, would you be leaving yourself open to a similar weakness with regards to open source OS development for Unix varients?

[Joey2cool]

I was wondering the same thing about SCO - by poking about in the Linux guts, would you be leaving yourself open to a similar weakness with regards to open source OS development for Unix varients?

First it would have to be decided if their code was used in linux

[singe]

First it would have to be decided if their code was used in linux

True, but as you've noted it could be decided that their code was used inappropriately, however silly such a judgement may be. And it's only recently that the damning evidence against SCO has come to light in the public domain - in the early days it was something that I thought about, and I'm probably not alone.

[bascule]

NT object manager

I was hoping to get a peek into the internals of the Windows NT object manager, which can be utilized to multiplex more than 64 event object handles simultaneously, a rather silly limitation of WaitForMultipleObjects() and by implecation, the entire Win32 event system. Unfortunately this did not appear to be amoung the leaked code...

[highwizard]

I was hoping to get a peek into the internals of the Windows NT object manager, which can be utilized to multiplex more than 64 event object handles simultaneously, a rather silly limitation of WaitForMultipleObjects() and by implecation, the entire Win32 event system. Unfortunately this did not appear to be amoung the leaked code...

Coincidence? I think not.

[astcell]

Send the code to the MAC folks, they will enjoy a good laugh.

[Gadsden]

Of course, if GNU code is found in the windows code... that could be interesting..