Cobra fails to Run Hello World

[jonathandavid]

I'm a little confused. If Cobra is "frozen" on .NET 2.0, shouldn't it be frozen as well with respect to Mono? Otherwise I predict a very grim future for the maintenance of Cobra, with every new version of Mono breaking some random part of the code.

[Charles]

The fix I have in mind will make Cobra more robust. It will still work on Mono 2.0 and .NET 2.0, but will also work on Mono 2.2.

If Cobra is ever in need of similar improvements for subsequent versions of .NET, I'm willing to make them.

[Charles]

I've made the robustness fix for Mono 2.2's different reflection order on "implements". However, the Mono 2.2 bug regarding string literals remains. They have already fixed this in development which meant my bug report to them was a duplicate. But it's not clear if they will be making a 2.2.x maintenance release, or if you'll just have to wait for the next version, 2.4, to get this.

So in the mean time, you should stick with Mono 2.0.

All test cases on .NET 2.0 still pass.

[gauthier]

The other is that System.Reflection in Mono 2.2 returns interfaces for IList<of T> in a different order than earlier versions and Cobra is sensitive to the order. I will make Cobra insensitive to the order.

I recall getting some issues with type hierarchy that implemented an heavy amount of interfaces because of the order of them (and having some type.GetInterfaces usage), I think making cobra order insensitive will solve that.

It seems there is no specified order for cli compilers (or for the clr?) when inspecting type inheritance/implementation chain.

[Charles]

I received an announcement email today that Mono 2.4 Preview 3 is available at:
http://mono.ximian.com/monobuild/previe ... d-preview/

I installed it on Mac OS X, ran the Cobra test suite and did an install-from-workspace. The problems we experienced in Mono 2.2 are gone.

-Chuck