[Mono-dev] Re: Ambiguous matching in method resolution
eyala at mainsoft.com
Thu Jun 1 05:37:06 EDT 2006
Are the interfaces implemented by the same class? This could explain quite a bit, actually.
On Thu, 1 Jun 2006 pablosantosluac at terra.es wrote:
> Date: Thu, 1 Jun 2006 10:33:19 +0200
> From: pablosantosluac at terra.es
> To: mono-devel-list at lists.ximian.com, Robert Jordan <robertj at gmx.net>
> Subject: Re: [Mono-dev] Re: Ambiguous matching in method resolution
> Well, the funny thing is that the problems I detected are between methods
> in... different interfaces!!
> ----- Original Message ----- From: "Robert Jordan" <robertj at gmx.net>
> To: <mono-devel-list at lists.ximian.com>
> Sent: Thursday, June 01, 2006 9:33 AM
> Subject: [Mono-dev] Re: Ambiguous matching in method resolution
>> Ympostor wrote:
>>> pablosantosluac at terra.es escribió:
>>>> And more info yet.
>>>> The methods that seem to have trouble are the following:
>>>> - The server is "publishing" several interfaces under different
>>>> "service names" by remoting.
>>>> - There are methods with the same name and different signatures on
>>>> different interfaces.
>>>> - These methods are the ones causing trouble (not even overloaded
>>>> methods on the same interface, but methods with the same name on
>>>> different ones)
>>> Just wondering... I have also experimented this exception when using
>>> Remoting and methods with the same name (overloaded). Have you tested
>>> the scenario Windows+MS.NET vs Windows+MS.NET? If yes and it works, the
>>> objective is to find a small testcase where the behaviour differs from
>>> one runtime to another.
>> It looks like this bug:
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list