"Hasani (remove nospam from address)" <hblackwell@n0sp4m.popstick.com> wrote
in message news:%23P$BFpfbEHA.3596@tk2msftngp13.phx.gbl...
> Will 2.0 or some other future version of the clr have support for
covariant
> returns?

>
> "Hasani (remove nospam from address)" <hblackwell@n0sp4m.popstick.com>
> wrote
> in message news:%23P$BFpfbEHA.3596@tk2msftngp13.phx.gbl...
>> Will 2.0 or some other future version of the clr have support for
> covariant
>> returns?
>
> Covariance works in Eiffel under CLR 1.1 today, so it's not impossible to
> implement, merely difficult -- although I'm fairly sure that this is
> strictly an Eiffel language feature that the compiler manages for you,
> just
> like their support for generics and MI. The generated IL is some complex
> kungfu.
>

> --
> Mickey Williams
> Author, "Visual C# .NET Core Ref", MS Press
> www.neudesic.com
> www.servergeek.com
>
>
>

>
> For example, Eiffel covariance most likely only works in Eiffel, I doubt a
> C# class calling it is going to be terribly pleased(infact it may not be
> able to deal with the class at all, I dunno).

> > Covariance works in Eiffel under CLR 1.1 today, so it's not impossible
to
> > implement, merely difficult -- although I'm fairly sure that this is
> > strictly an Eiffel language feature that the compiler manages for you,
> > just
> > like their support for generics and MI. The generated IL is some complex
> > kungfu.

> "Daniel O'Connell [C# MVP]" <onyxkirx@--NOSPAM--comcast.net> wrote in
> message news:Oru9JcqbEHA.3524@TK2MSFTNGP12.phx.gbl...
>>
>> For example, Eiffel covariance most likely only works in Eiffel, I doubt
>> a
>> C# class calling it is going to be terribly pleased(infact it may not be
>> able to deal with the class at all, I dunno).
>
> That's true - if you look at the IL, the object returned is an instance of
> the anchor type. It's strictly an Eiffel language thing - not too
> suprising,
> since so few languages support covariance for fields, parameters, and
> results. That's why I wrote these lines in:
> message news:OujQh8nbEHA.1644@tk2msftngp13.phx.gbl...
>
>> > Covariance works in Eiffel under CLR 1.1 today, so it's not impossible
> to
>> > implement, merely difficult -- although I'm fairly sure that this is
>> > strictly an Eiffel language feature that the compiler manages for you,
>> > just
>> > like their support for generics and MI. The generated IL is some
>> > complex
>> > kungfu.
>
> Strictly an Eiffel language feature...

>
> --
> Mickey Williams
> Author, "Visual C# .NET Core Ref", MS Press
> www.neudesic.com
> www.servergeek.com
>
>

>
> "Mickey Williams [C# MVP]" <my first name at servergeek dot com> wrote in
> message news:%23nDjNwrbEHA.1048@tk2msftngp13.phx.gbl...
> > "Daniel O'Connell [C# MVP]" <onyxkirx@--NOSPAM--comcast.net> wrote in
> > message news:Oru9JcqbEHA.3524@TK2MSFTNGP12.phx.gbl...
> >>
> >> For example, Eiffel covariance most likely only works in Eiffel, I
doubt
> >> a
> >> C# class calling it is going to be terribly pleased(infact it may not
be
> >> able to deal with the class at all, I dunno).
> >
> > That's true - if you look at the IL, the object returned is an instance
of
> > the anchor type. It's strictly an Eiffel language thing - not too
> > suprising,
> > since so few languages support covariance for fields, parameters, and
> > results. That's why I wrote these lines in:
> > message news:OujQh8nbEHA.1644@tk2msftngp13.phx.gbl...
> >
> >> > Covariance works in Eiffel under CLR 1.1 today, so it's not
impossible
> > to
> >> > implement, merely difficult -- although I'm fairly sure that this is
> >> > strictly an Eiffel language feature that the compiler manages for
you,
> >> > just
> >> > like their support for generics and MI. The generated IL is some
> >> > complex
> >> > kungfu.
> >
> > Strictly an Eiffel language feature...
>
> Ya, I missed the "strictly" in that. Sorry, ;). I am curious if methods
with
> covariant return types work in other languages or if they cause the
> compilers to balk. To lazy to find and try eiffel though.
> >
> > --
> > Mickey Williams
> > Author, "Visual C# .NET Core Ref", MS Press
> > www.neudesic.com
> > www.servergeek.com
> >
> >
>
>

"Hasani (remove nospam from address)" <hblackwell@n0sp4m.popstick.com> wrote
in message news:OzNOecybEHA.3804@TK2MSFTNGP10.phx.gbl...
> Well, created my post with c++.net and c# in mind.
> What is the definition of a method/function signature, I thought it a
> function's name, and the parameters/arguments. The return type can be
> different
> so
> int Foo()
> void Foo()
> const char* Foo()
>
> all have the same method/function signature.
>