double casted to IMyInterface

[nemerle fanboy]

The other day I casted a bool to an interface explicitly. The compiler
was ok.
When I invoked the methods I got a run-time exception (entry point not
found).

Is it a compiler bug?

[VladD2]

2008/10/23 nemerle fanboy <nemerle...@yahoo.it>:

> The other day I casted a bool to an interface explicitly. The compiler
> was ok.
> When I invoked the methods I got a run-time exception (entry point not
> found).

Code like:
WriteLine((true : IConvertible).ToInt32(null));
work fine.
What do you mean?

[nemerle fanboy]

Sorry for the delay. I'm having problems with google groups.

Can I assume true actually implements IConvertible?

double doesn't implement IMyFunnyInterface.
A explicit cast was provided (it returns a wrapper object implementing
that interface) but, probably because it was defined in the wrong
place, it was not called (breakpoint not hit).

The double was converted anyway and passed to a function as argument,
causing said runtime exception.

Is it by design?

On Oct 23, 6:53 pm, VladD2 <v...@rsdn.ru> wrote:
> 2008/10/23 nemerle fanboy <nemerle.is_c...@yahoo.it>:

[Dmitry Ivankov]

On Mon, Oct 27, 2008 at 5:42 AM, nemerle fanboy <nemerle...@yahoo.it> wrote:

Sorry for the delay. I'm having problems with google groups.

Can I assume true actually implements IConvertible?

double doesn't implement IMyFunnyInterface.
A explicit cast was provided (it returns a wrapper object implementing
that interface) but, probably because it was defined in the wrong
place, it was not called (breakpoint not hit).

The double was converted anyway and passed to a function as argument,
causing said runtime exception.

Is it by design?

Currently explicit conversions are looked up only in "from" type.

It should be either allowed to define them in other places or give a warning/error if we are trying to define conversion operator with from not equal to (or maybe  +some inheritance stuff) the declaring class.

Generating invalid IL is a bug itself in any case.