The reason is more that Unity has a custom mono version and needs to port their fixes and changes over without breaking too much (as mono 2.6 to mono 2.10 is codebase wise a breaking update due to the GC and memory changes). If Mono 2.8 reaches total stability before you start thinking about Unity 5, can we expect a Mono upgrade before the next major release of Unity? Is it a stability thing? That is, are you waiting for Mono to declare 2.8 a stable release? I thought you were going to upgrade to Mono 2.8 with the next major release of Unity, and was really looking forward to this. The garbage collector prior to 2.8 has been bothering me for well over a year. There are quite a few of us out here who're dying to get a garbage collector that is not only generational, but compacts the heap properly after cleanup, so we can get rid of the memory issues that arise when allocation heap becomes fragmented over time. ) Can you provide an explanation on why you're aiming for 2.6, when 2.8 includes the entirity of C# 4.0 and more importantly, a new and improved garbage collector? This makes me curious, because I think that's a really bad idea. I read today on this website, that you intend to ship Unity 4 with Mono 2.6.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |