[Mono-list] Contributing to the classes.

[Rhys Weatherley]

Sebastien Lambla wrote:

> Moreover, the Microsoft articles themselves say to use ILDASM to see what's
> behind the class library...

That won't protect you unless you use a three-step clean room process:
disassemble, write an abstract description, and then hand the description
to someone else, who hasn't seen the original, to implement.

Microsoft encourages the use of ILDASM for people who are writing
programs on top of their libraries, and who can't glean enough info
from the documentation to know what is going on.  They do not encourage
it for those who are re-engineering the libraries.  The code is still Copyright

Microsoft, and so you would technically be creating a derived work
unless you used the clean room process above.

Be careful.

Cheers,

Rhys.