[Mono-dev] Re: Ambiguous matching in method resolution

Eyal Alaluf eyala at mainsoft.com
Thu Jun 1 05:55:16 EDT 2006


>From my experience it's better to reduce the application to a small sample. During this effort you may stumble upon extra factors that are part of the bug that would be easier to workaround and important for getting the bug fixed.

Eyal.

On Thu, 1 Jun 2006 pablosantosluac at terra.es wrote:

> Date: Thu, 1 Jun 2006 11:45:38 +0200
> From: pablosantosluac at terra.es
> To: Eyal Alaluf <eyala at mainsoft.com>
> Cc: mono-devel-list at lists.ximian.com
> Subject: Re: [Mono-dev] Re: Ambiguous matching in method resolution
> 
> Hi,
>
> No, every interface is implemented by a different class.
>
> Do you think is better to rename all the methods or wait for a solution?
>
> pablo
>
> ----- Original Message ----- From: "Eyal Alaluf" <eyala at mainsoft.com>
> To: <pablosantosluac at terra.es>
> Cc: <mono-devel-list at lists.ximian.com>; "Robert Jordan" <robertj at gmx.net>
> Sent: Thursday, June 01, 2006 11:37 AM
> Subject: Re: [Mono-dev] Re: Ambiguous matching in method resolution
>
>
>> Hi.
>> 
>> Are the interfaces implemented by the same class? This could explain quite 
>> a bit, actually.
>> 
>> Eyal.
>> 
>> 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:
>>>> 
>>>> http://bugzilla.ximian.com/show_bug.cgi?id=77191
>>>> 
>>>> Robert
>>>> 
>>>> _______________________________________________
>>>> Mono-devel-list mailing list
>>>> Mono-devel-list at lists.ximian.com
>>>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>> 
>>> _______________________________________________
>>> Mono-devel-list mailing list
>>> Mono-devel-list at lists.ximian.com
>>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>> 
>
>


More information about the Mono-devel-list mailing list