[Mono-devel-list] Mono.Posix Structuring
tberman at off.net
Fri Sep 24 02:24:09 EDT 2004
On Thu, 2004-09-23 at 21:14 -0400, Jonathan Pryor wrote:
> This would prevent lots of different methods from being presented in the
> same class, assuming that IEEE did their job and kept similar functions
> together when they standardized the header files.
The only potential issue I see with this is existing code.
Considering that mono 1.0 is out, and that people are publishing
software using these APIs, it would be nice not to break their stuff.
For existing, bound functionality, it would be great if we could
maintain source and binary compatibility by keeping bound content where
It would be nice to keep this stuff as-is at least until the mono 1.1.x
series has a real 1.2 release, and people don't have to track
potentially both APIs (with the old stuff on the 1.0 branch and release
line, and the new stuff on the 1.1 release line/HEAD).
More information about the Mono-devel-list