this keyword problem

[Timothy V]

Hi everyone,
I'm having trouble with the keyword this inside a class. The following code
is an example of the problem, not what I am actually doing.

public class C
{
public C() {}
public string s;
public void Function()
{
C c = new C();
this = c;
}
}

Basically it brings a compiler error CS1604 (Cannot assign to 'variable'
because it is read-only).

My question is, how can I do this? Is it possible?

Thank you,

Tim.

[Jon Skeet [C# MVP]]

Timothy V <tr****@msn.com> wrote:

I'm having trouble with the keyword this inside a class. The following code
is an example of the problem, not what I am actually doing.

public class C
{
public C() {}
public string s;
public void Function()
{
C c = new C();
this = c;
}
}

Basically it brings a compiler error CS1604 (Cannot assign to 'variable'
because it is read-only).

My question is, how can I do this? Is it possible?

You can't. Why would you want to?

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

[Morten Wennevik]

Hi Timothy,

Eh, what are you trying to do? You can't change 'this', and why would you want to?

--
Happy coding!
Morten Wennevik [C# MVP]

[Timothy V]

hehehe, well, I have a method that deserializes a an xml file and i would
like to assign 'this' as the object that the deserializer returns.

Its ok, i was just wondering if it was at all possible. I'll do it another
way.

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

Timothy V <tr****@msn.com> wrote:

I'm having trouble with the keyword this inside a class. The following
code
is an example of the problem, not what I am actually doing.

public class C
{
public C() {}
public string s;
public void Function()
{
C c = new C();
this = c;
}
}

Basically it brings a compiler error CS1604 (Cannot assign to 'variable'
because it is read-only).

My question is, how can I do this? Is it possible?

You can't. Why would you want to?

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

[Uri Dor]

'this' is a pointer to the "current" object, which is the object on
which the method was called.
if you reached Function(), which is a non-static method, you definitely
already have an instance of class C.
No, it is not possible to assign to 'this', and if you think hard,
there's no point in doing that in the first place.

Timothy V wrote:

Hi everyone,
I'm having trouble with the keyword this inside a class. The following code
is an example of the problem, not what I am actually doing.

public class C
{
public C() {}
public string s;
public void Function()
{
C c = new C();
this = c;
}
}

Basically it brings a compiler error CS1604 (Cannot assign to 'variable'
because it is read-only).

My question is, how can I do this? Is it possible?

Thank you,

Tim.

[Flare]

> No, it is not possible to assign to 'this', and if you think hard,

there's no point in doing that in the first place.

There would be a point. Conceptual you could assign the current objects this
pointer to another object's this pointer. This would make them equal. I
would be just like making a reference copy, just the other way around.

But then again...you can´t, and you could obtain the above logic in a more
transparent way.

Anders Jacobsen

[Gawel]

> hehehe, well, I have a method that deserializes a an xml file and i would

like to assign 'this' as the object that the deserializer returns.

Its ok, i was just wondering if it was at all possible. I'll do it another
way.

Try to do it in static method of your class. This pattern is used in may
..net classes,
for example Image Image.FromFile(String path)

--
Gawel
-------------------------------
Pierwszy ³yk z pucharu nauk przyrodniczych czyni ateist±, ale na dnie
pucharu czeka Bóg.
Werner Heisenberg

[Daniel O'Connell [C# MVP]]

"Flare" <no****@sorry.dk> wrote in message
news:On**************@tk2msftngp13.phx.gbl...

No, it is not possible to assign to 'this', and if you think hard,
there's no point in doing that in the first place.
There would be a point. Conceptual you could assign the current objects
this
pointer to another object's this pointer. This would make them equal. I
would be just like making a reference copy, just the other way around.

That actually doesn't work. this is an argument(argument 0), assigning it
would result in changing the this pointer *only* for the current method. The
only way to change that would be to change all this pointers into ref
arguments, which is far less enticing, IMHO.

As such assigning the this pointer, as it is, has no point. Thats a
considerable reason why the language offers *no* way to make such
assignments(of course, the general danger of the assignments is almost
certainly why the *runtime* chose not to make it possible by default)

But then again...you can´t, and you could obtain the above logic in a more
transparent way.

Anders Jacobsen

[Ted Miller]

"Daniel O'Connell [C# MVP]" <[e-mail]> wrote in
message news:%2****************@tk2msftngp13.phx.gbl...

That actually doesn't work. this is an argument(argument 0), assigning it
would result in changing the this pointer *only* for the current method. The only way to change that would be to change all this pointers into ref
arguments, which is far less enticing, IMHO.

As such assigning the this pointer, as it is, has no point. Thats a
considerable reason why the language offers *no* way to make such
assignments(of course, the general danger of the assignments is almost
certainly why the *runtime* chose not to make it possible by default)

I think he's trying to get behavior as if operator = was overloaded. So the
goal of "assigning" to this would not be to mess with the this pointer
itself, but rather to get some sort of duplication of the fields from the
rhs instance to the current object.

Since operator = is not overloadable in C#, this is a non-starter regardless
of how one feels about the idea.

[Timothy V]

Yup, that was all i really wanted to do.

I ended up using static methods instead.
"Ted Miller" <te*@nwlink.com> wrote in message
news:10*************@corp.supernews.com...

"Daniel O'Connell [C# MVP]" <[e-mail]> wrote in
message news:%2****************@tk2msftngp13.phx.gbl...

That actually doesn't work. this is an argument(argument 0), assigning it
would result in changing the this pointer *only* for the current method.

The

only way to change that would be to change all this pointers into ref
arguments, which is far less enticing, IMHO.

As such assigning the this pointer, as it is, has no point. Thats a
considerable reason why the language offers *no* way to make such
assignments(of course, the general danger of the assignments is almost
certainly why the *runtime* chose not to make it possible by default)

I think he's trying to get behavior as if operator = was overloaded. So
the
goal of "assigning" to this would not be to mess with the this pointer
itself, but rather to get some sort of duplication of the fields from the
rhs instance to the current object.

Since operator = is not overloadable in C#, this is a non-starter
regardless
of how one feels about the idea.

[Daniel O'Connell [C# MVP]]

"Ted Miller" <te*@nwlink.com> wrote in message
news:10*************@corp.supernews.com...

"Daniel O'Connell [C# MVP]" <[e-mail]> wrote in
message news:%2****************@tk2msftngp13.phx.gbl...

That actually doesn't work. this is an argument(argument 0), assigning it
would result in changing the this pointer *only* for the current method.

The

only way to change that would be to change all this pointers into ref
arguments, which is far less enticing, IMHO.

As such assigning the this pointer, as it is, has no point. Thats a
considerable reason why the language offers *no* way to make such
assignments(of course, the general danger of the assignments is almost
certainly why the *runtime* chose not to make it possible by default)

I think he's trying to get behavior as if operator = was overloaded. So
the
goal of "assigning" to this would not be to mess with the this pointer
itself, but rather to get some sort of duplication of the fields from the
rhs instance to the current object.

Since operator = is not overloadable in C#, this is a non-starter
regardless
of how one feels about the idea.

Perhaps, but if you are already able to access this, you can access the
fields, ;).

I can see the point, however I disagree with it as it entirely breaks C#
semantics and really just isn't a good idea. I also am not particularly
convinced you could write it with an overloadable = operator without runtime
support.