2 Oct 2006 09:42
Re: Suggestion: Mono.Collection really useful
Michael J. Ryan <tracker1_lists <at> theroughnecks.com>
2006-10-02 07:42:27 GMT
2006-10-02 07:42:27 GMT
Hello Francisco, I think you may be more interested in the mono-list (for those using mono/C#), as this is the mono-devel-list for internal development of the mono framework/platform. First, regarding compatibility, C# and the .Net CLI are ECMA and ISO standards at this point, so it is important to maintain that as a base/minimum level. Beyond this, the most widely used implementation is Microsoft's, which does include segments other than what was submitted to ECMA and ISO. Some of these extensions are more important than others to the mono framework (ex: ASP.Net support). There are some things you may or may not agree with inside the core system, but the fact is, compatibility is pretty important as .Net (MS, Mono, dot-gnu etc) lends itself to cross-platform development. Though most of what will be developed in mono will probably center around Linux development. Many (myself included) would like to see more projects work across varied platforms without issue, or at least with less issue. Even though .Net started as a Microsoft "standard," we should at least respect the core of the standard... MS has a history of breaking accepted standards, I don't think it would benefit mono to follow that path. Moreover, if there is more there than you need, so be it, better than there being less than you need. I find it very handy that most collections can be used like arrays in code (foreach is my friend). I've used this for strings/chars quite a bit. It tends to keep the app-level code a bit cleaner, and easier to understand, even if it doesn't fit the separation in your mind.(Continue reading)
RSS Feed