type casting confusion

[Wayne M J]

I have worked out most type casting [(int)char] and the likes but I am
curious about one aspect.

Endpoint ep...;
IPEndPoint iep...;
....
ep = (EndPoint)iep;
....
iep = (IPEndPoint)ep;
....

For some reason the above works
(http://www.wmjackson.cable.nu/website/goto.aspx?ID=4) but what I do not
understand is why?

Oddly enough, it was the only way for me to accomplish my task.

[Jon Skeet [C# MVP]]

Wayne M J <no*@home.nor.bigpuddle.com> wrote:

I have worked out most type casting [(int)char] and the likes but I am
curious about one aspect.

Endpoint ep...;
IPEndPoint iep...;
...
ep = (EndPoint)iep;
...
iep = (IPEndPoint)ep;
...

For some reason the above works
(http://www.wmjackson.cable.nu/website/goto.aspx?ID=4) but what I do not
understand is why?

Oddly enough, it was the only way for me to accomplish my task.

Why would you expect it not to work? You don't actually need the cast
in the first one - you can just do:

ep = iep;

because EndPoint is the base class of IPEndPoint.

Don't forget that the variables ep and iep just hold references to
objects. Casting the reference doesn't change the type of the object at
all.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Wayne M J]

"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message
news:MP************************@msnews.microsoft.c om...

Why would you expect it not to work? You don't actually need the cast
in the first one - you can just do:

ep = iep;

because EndPoint is the base class of IPEndPoint.
When I did the ep = iep; it complained about an implicit cast.

That was when I originally wrote the code under VS.Net2002.
Don't forget that the variables ep and iep just hold references to
objects. Casting the reference doesn't change the type of the object at
all.

Actually I just reread the dox and this is the where I am sure I got the
idea from:
ms-help://MS.MSDNQTR.2003FEB.1033/cpref/html/frlrfSystemNetSocketsSocketClas
sReceiveFromTopic.htm

[Jon Skeet [C# MVP]]

Wayne M J <no*@home.nor.bigpuddle.com> wrote:

"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message
news:MP************************@msnews.microsoft.c om...

Why would you expect it not to work? You don't actually need the cast
in the first one - you can just do:

ep = iep;

because EndPoint is the base class of IPEndPoint.

When I did the ep = iep; it complained about an implicit cast.

That was when I originally wrote the code under VS.Net2002.

What exactly do you mean by "complained"? What did it say, exactly?
Could you reproduce it?

Don't forget that the variables ep and iep just hold references to
objects. Casting the reference doesn't change the type of the object at
all.

Actually I just reread the dox and this is the where I am sure I got the
idea from:
ms-help://MS.MSDNQTR.2003FEB.1033/cpref/html/frlrfSystemNetSocketsSocketClas
sReceiveFromTopic.htm

The cast in that code is unnecessary too. For instance:

using System;
using System.Net;

public class Test
{
static void Main()
{
IPEndPoint sender = new IPEndPoint(IPAddress.Any, 0);
EndPoint senderRemote = sender;
}
}

compiles with no problems.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[100]

Hi Wayne,

IPEndPoint inherits from EndPoint type. So IPEndPoint *is* EndPoint. you can
either reference IPEndPoint objects using IPEndPoint variables or EndPoint
variables.
You don't have to use explicit cast here.

So, legal implicit casts are:
IPEndPoint ipep = .....
EndPoint ep = ipep;
object obj = ipep;

B\rgds
100

"Wayne M J" <no*@home.nor.bigpuddle.com> wrote in message
news:uK*************@TK2MSFTNGP11.phx.gbl...

"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message
news:MP************************@msnews.microsoft.c om...

Why would you expect it not to work? You don't actually need the cast
in the first one - you can just do:

ep = iep;

because EndPoint is the base class of IPEndPoint.
When I did the ep = iep; it complained about an implicit cast.

That was when I originally wrote the code under VS.Net2002.

Don't forget that the variables ep and iep just hold references to
objects. Casting the reference doesn't change the type of the object at
all.

Actually I just reread the dox and this is the where I am sure I got the
idea from:

ms-help://MS.MSDNQTR.2003FEB.1033/cpref/html/frlrfSystemNetSocketsSocketClas sReceiveFromTopic.htm

[Wayne M J]

"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message
news:MP************************@msnews.microsoft.c om...

What exactly do you mean by "complained"? What did it say, exactly?
Could you reproduce it?

"Cannot implicitly convert 'IPEndPoint' to 'EndPoint'"

But I have just rebuilt the app using the 'ep = iep' and it worked fine.

This I do not understand - is there an equivalent to VB's "Option Strict"
under C#?

[Jon Skeet [C# MVP]]

Wayne M J <no*@home.nor.bigpuddle.com> wrote:

"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message
news:MP************************@msnews.microsoft.c om...

What exactly do you mean by "complained"? What did it say, exactly?
Could you reproduce it?
"Cannot implicitly convert 'IPEndPoint' to 'EndPoint'"

That sounds very odd, as it definitely *can* implicitly convert
IPEndPoint to EndPoint. I don't suppose you were trying to pass a
parameter by reference, were you? That would produce an error such as:

Test.cs(13,18): error CS1503: Argument '1': cannot convert from 'ref
System.Net.IPEndPoint' to 'ref System.Net.EndPoint'

which isn't quite the same, but is far more understandable.
(Reference/out parameters must match in type *exactly*.)
But I have just rebuilt the app using the 'ep = iep' and it worked fine.
So you can't actually reproduce it now? Hmmm...
This I do not understand - is there an equivalent to VB's "Option Strict"
under C#?

No - C# is always typesafe.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Wayne M J]

"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message
news:MP************************@msnews.microsoft.c om...

That sounds very odd, as it definitely *can* implicitly convert
IPEndPoint to EndPoint. I don't suppose you were trying to pass a
parameter by reference, were you? That would produce an error such as:

Test.cs(13,18): error CS1503: Argument '1': cannot convert from 'ref
System.Net.IPEndPoint' to 'ref System.Net.EndPoint'

which isn't quite the same, but is far more understandable.
(Reference/out parameters must match in type *exactly*.)

But I have just rebuilt the app using the 'ep = iep' and it worked fine.

So you can't actually reproduce it now? Hmmm...

This I do not understand - is there an equivalent to VB's "Option

Strict" under C#?

No - C# is always typesafe.

The machine I originally wrote the code on had VS6, VS2002 and VS2003; I
wonder if that may have cause a problem.

The current system only has VS6 and VS2003 installed.