Hello Martin,
On Sun, 2005-11-06 at 18:16 +, Martin Hinks wrote:
> Hi all,
>
> I do not understand the binary compatibility issue entirely.
The "binary compatibility" I talked about only applies to
Mono.Security.dll (and other Mono.* assemblies that don't change their
version numbers with each Mono release).
> For example,
>
> To be compatible with FX 2.0 System.Net.Security.SslProtocolType.cs
> needs public enum SslProtocolType renamed to public enum SslProtocols.
>
> What are the implications of the "binary compatibility" for this
> change for example please?
That's another kind of binary compatibility that we track using the
class status page.
--
Sebastien Pouliot
email: [EMAIL PROTECTED]
blog: http://pages.infinit.net/ctech/
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
