How To overload =

[Harry J. Smith]

How do you overload the = operator?

public static MultiUI operator = (MultiUI left, MultiUI right)

{

return right;

}

gives an error of "overloadable binary operator expected"

-Harry

[cody]

You cannot overload operator=, but you can overload the type conversion
operator.
According to your example what sense would it make to overload operator=
which only assign one objects of type T to another object with exact the
same type?

--
cody

[Freeware, Games and Humor]
www.deutronium.de.vu || www.deutronium.tk
"Harry J. Smith" <hj*****@ix.netcom.com> schrieb im Newsbeitrag
news:A6*****************@newsread2.news.pas.earthl ink.net...

How do you overload the = operator?

public static MultiUI operator = (MultiUI left, MultiUI right)

{

return right;

}

gives an error of "overloadable binary operator expected"

-Harry

[Daniel Billingsley]

Yeah, what he said. :)

I thought I needed to overload = to create my own string-like class until I
read this article where I learned overloading the type conversion did the
trick.

http://www.c-sharpcorner.com/1/SuperStringMG.asp

"cody" <pl*************************@gmx.de> wrote in message
news:ei****************@TK2MSFTNGP11.phx.gbl...

You cannot overload operator=, but you can overload the type conversion
operator.
According to your example what sense would it make to overload operator=
which only assign one objects of type T to another object with exact the
same type?

[Harry J. Smith]

When you do a = b, where a and b are two objects, only the pointer to b is copied so a and b are the same object. The disassembly
shows:

a = b;

000000d7 mov edi,dword ptr [ebp-18h]

I wanted a function to copy all of the fields of b to a and have two objects whose fields are currently equal. I can do this with a
function like SetTo(b, a), but I wanted to do it with the = operator. This may be a bad idea because if you could do it you would
loose the copy pointer method.

-Harry

"cody" <pl*************************@gmx.de> wrote in message news:ei****************@TK2MSFTNGP11.phx.gbl...

You cannot overload operator=, but you can overload the type conversion
operator.
According to your example what sense would it make to overload operator=
which only assign one objects of type T to another object with exact the
same type?

--
cody

[Freeware, Games and Humor]
www.deutronium.de.vu || www.deutronium.tk
"Harry J. Smith" <hj*****@ix.netcom.com> schrieb im Newsbeitrag
news:A6*****************@newsread2.news.pas.earthl ink.net...

How do you overload the = operator?

public static MultiUI operator = (MultiUI left, MultiUI right)

{

return right;

}

gives an error of "overloadable binary operator expected"

-Harry

[Jon Skeet [C# MVP]]

Harry J. Smith <hj*****@ix.netcom.com> wrote:

When you do a = b, where a and b are two objects, only the pointer to
b is copied so a and b are the same object. The disassembly
shows:

a = b;

000000d7 mov edi,dword ptr [ebp-18h]

I wanted a function to copy all of the fields of b to a and have two
objects whose fields are currently equal. I can do this with a
function like SetTo(b, a), but I wanted to do it with the = operator.
This may be a bad idea because if you could do it you would
loose the copy pointer method.

So you want value type semantics for assignment. Do you need reference
type semantics elsewhere, or could you just make your type a reference
type?

Don't forget that assignments effectively happen elsewhere - what would
you want to happen when someone passed a parameter? Should that make a
new object or not?

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

[Stu Smith]

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

Harry J. Smith <hj*****@ix.netcom.com> wrote:

When you do a = b, where a and b are two objects, only the pointer to
b is copied so a and b are the same object. The disassembly
shows:

a = b;

000000d7 mov edi,dword ptr [ebp-18h]

I wanted a function to copy all of the fields of b to a and have two
objects whose fields are currently equal. I can do this with a
function like SetTo(b, a), but I wanted to do it with the = operator.
This may be a bad idea because if you could do it you would
loose the copy pointer method.
So you want value type semantics for assignment. Do you need reference
type semantics elsewhere, or could you just make your type a reference
type?

Didn't you mean to say "...or could you just make your type a _value_ type?"

Don't forget that assignments effectively happen elsewhere - what would
you want to happen when someone passed a parameter? Should that make a
new object or not?

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

[Jon Skeet [C# MVP]]

Stu Smith <st*****@nospam-digita.com> wrote:

So you want value type semantics for assignment. Do you need reference
type semantics elsewhere, or could you just make your type a reference
type?

Didn't you mean to say "...or could you just make your type a _value_ type?"

Yup. Oops.

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