> Miguel, if we don't want to extend the official class library why not > do it the way the SDF does it for .NET CF? Mono could provide a > separate enumeration/attribute/etc. in a Mono namespace, call it the > same or <origName>Ex and extend that "copy" using an Adapter pattern > or inheritance where possible (for example to enhance > System.Windows.Forms.Application they have > OpenNetCF.Windows.Forms.ApplicationEx I believe). That'll still not > work on .NET but would be a clean way to let Mono developers do their > work while clarifying through the namespace and reference to an > assembly that it's an extension.
Putting the enumeration elsewhere is just as bad as adding to an existing enumeration. There is no difference from breaking the API standpoint. It can be done, but we have so far had a policy of not breaking the API. Changing this policy will require a lot of convincing, and with alternatives in place (like custom marshalling) it will be hard to make a case for this. _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
