Re: [Mono-dev] [Patch] gmcs considers bla and bla{T} as illegal in a cref

2009-05-17 Thread Atsushi Eno
Novell bugzilla is too buggy to let me post my comments so I write here instead: It's not a fix but just a workaround, as it skips further syntax checks such as: /// .. and optionally worse, error generation in the output xml such as Atsushi Eno Eberhard Beilharz wrote: > gmcs gives warning C

[Mono-dev] [PATCH] COM Interop - Support for out parameters of type SAFEARRAY[VARIANT]

2009-05-17 Thread Sylvain Dupont
Hi, The patch attached adds support for marshalling out parameters of type SAFEARRAY[VARIANT]. In addition to the tests included in the patch, I have also tested this successfully against other COM components, both on Windows and Linux (using Mainwin and with the MONO_COM environment variable set

Re: [Mono-dev] [Patch] gmcs considers bla and bla{T} as illegal in a cref

2009-05-17 Thread Andreas Färber
Am 17.05.2009 um 21:16 schrieb Eberhard Beilharz: > > Andreas Färber wrote: >> >> Am 16.05.2009 um 22:33 schrieb Eberhard Beilharz: >> >>> gmcs gives warning CS1584 if you have an XML comment referencing a >>> generic type like cref="Bla" or cref="Bla{T}". Those two variants >>> work with Microso

Re: [Mono-dev] [Patch] gmcs considers bla and bla{T} as illegal in a cref

2009-05-17 Thread Eberhard Beilharz
Andreas Färber wrote: > > Am 16.05.2009 um 22:33 schrieb Eberhard Beilharz: > >> gmcs gives warning CS1584 if you have an XML comment referencing a >> generic type like cref="Bla" or cref="Bla{T}". Those two variants >> work with Microsoft's csc. The only variant that makes gmcs happy is >> cref=

[Mono-dev] Bug #360455

2009-05-17 Thread Stefan Noack
I've been trying to fix https://bugzilla.novell.com/show_bug.cgi?id=360455. "(g)mcs erroneously raises "x is never used" warning CS0067 with public events" This happens when the containing class is generic but the event does not use the generic type in it's signature. Therre is another test case

Re: [Mono-dev] [Mono-list] Bug with OutputCache directive in Mono 2.4.1

2009-05-17 Thread Maxim
Hi Marek! It seems like Mono 2.4.1 removed from Yast repository? I've tried to upgrade Mono again, but can't find version newer than 2.4-19.1. It was something temporal or my mistake? Later I've compiled Mono 2.4.1 from sources from SVN and run my application on xsp2. It seems like everything is

Re: [Mono-dev] Compiling Mono v2.4 RC2 (Solaris 10 SPARCv9)

2009-05-17 Thread chris zhu
I debug into mono/mini/local-propagation.c of mono 2.2, and found there's something wrong in the "MonoBasicBlock *bb" of function mono_local_deadce. The point of previous inst is same as the inst itself, which will run into dead lock if we traverses the inst list backward. It's hard for us to go

Re: [Mono-dev] [Ximian-mono-list] Please take a look at the test-Microsoft_Build_Engine-2.0 failure on mono-branch.

2009-05-17 Thread Ankit Jain
Already working on it, thanks for the heads up though! -Ankit Marc Christensen wrote: > Hi everyone, > > We have a test-Microsoft_Build_Engine-2.0 failure on mono-branch which > started between -r131512:131591. I'm having trouble tracking down what > broke it. It seems that commits during that

Re: [Mono-dev] Compiling Mono v2.4 RC2 (Solaris 10 SPARCv9)

2009-05-17 Thread snarayan
Thracx wrote: > > > pablosantosl...@terra.es wrote: >> >> Last one I tried and build was 2.2. We're using it to test Plastic every >> week on OpenSolaris. The binaries are available at Blastwave, but never >> tried 2.4 > > You have a working build of Mono v2.2 on SPARC? I received the same

Re: [Mono-dev] [Patch] gmcs considers bla and bla{T} as illegal in a cref

2009-05-17 Thread Andreas Färber
Am 16.05.2009 um 22:33 schrieb Eberhard Beilharz: > gmcs gives warning CS1584 if you have an XML comment referencing a > generic type like cref="Bla" or cref="Bla{T}". Those two variants > work with Microsoft's csc. The only variant that makes gmcs happy is > cref="T:Bla`1" which gives a warning