object

[TonyJ]

Hello!

I have read this small example on some page on the internet but I can't
understand
how myValue can be a member of the x object.becaude object is a reserved key
object.
The same question is also valid how the y object can contain the member
myValue?

object x = new object();
x.myValue = 10;
object y = x;
y.myValue = 20; // after this statement both x.myValue and y.myValue equal
20


//Tony

[Jon Skeet [C# MVP]]

Re: object

On Feb 18, 11:16 am, "TonyJ" <johansson.ande rs...@telia.com wrote:

I have read this small example on some page on the internet but I can't
understand how myValue can be a member of the x object.becaude
object is a reserved key
object.
The same question is also valid how the y object can contain the member
myValue?

It can't - the code you gave isn't valid. Where did you get the sample
from?

Jon

[TonyJ]

Re: object

Hello!

In this place

http://www.softsteel.co.uk/tutorials/cSharp/lesson4.html

//Tony

"Jon Skeet [C# MVP]" <skeet@pobox.co mskrev i meddelandet
news:eacc0166-dd63-46f8-baf4-8d920c651540@d5 g2000hsc.google groups.com...

On Feb 18, 11:16 am, "TonyJ" <johansson.ande rs...@telia.com wrote:

I have read this small example on some page on the internet but I can't
understand how myValue can be a member of the x object.becaude
object is a reserved key
object.
The same question is also valid how the y object can contain the member
myValue?

>
It can't - the code you gave isn't valid. Where did you get the sample
from?
>
Jon

[David Hearn]

Re: object

Jon Skeet [C# MVP] wrote:

TonyJ <johansson.ande rsson@telia.com wrote:

>In this place
>http://www.softsteel.co.uk/tutorials...p/lesson4.html

>
Right. It's probably worth dropping the author a mail to explain that
his code is broken then :)
>

The actual article says:

"Consider the following piece of code, in which two variables are given
a reference to the same object (for the sake of the example, this object
is taken to contain the numeric property 'myValue').

object x = new object();
x.myValue = 10;
object y = x;
y.myValue = 20; // after this statement both x.myValue and
y.myValue equal 20"

I guess, either the "for the sake of the example" (ie. this isn't valid
in real life) bit was missed, or it has just been added following
feedback from someone.

D