Thread: Creating new instance of an object

What if you did this:

Code:

myObject newObj = null;

instead of:

Code:

myObj newObj;

is it because it expects you to do something in if or else section???

Originally Posted by jmurrayhead

What if you did this:

Code:

myObject newObj = null;

instead of:

Code:

myObj newObj;

Yeah, I tried that and it seemed to stop the problem. Just wondered why it gives that error if I don't put = null...I thought it should be null by default.

It is null by default. And like I said, it's not an actual error. It's just a warning. It's basically saying that you haven't assigned it anything. This COULD be a problem if you didn't have the proper checks in place, i.e., if you didn't check if it was null it would result in an object reference error.

Originally Posted by micky

is it because it expects you to do something in if or else section???

There is something inside them in my code m. I was just using this to show the idea....

Don't think that would be a problem though.

Originally Posted by richyrich

There is something inside them in my code m. I was just using this to show the idea....

Don't think that would be a problem though.

i know i should'nt have said something

Originally Posted by jmurrayhead

It is null by default. And like I said, it's not an actual error. It's just a warning. It's basically saying that you haven't assigned it anything. This COULD be a problem if you didn't have the proper checks in place, i.e., if you didn't check if it was null it would result in an object reference error.

Yeah, that's pretty much what I thought. I wonder why it highlights the if condition rather than the original variable though...Never mind... Should be good to go now...

I just don't like anything in that box in VS...

Originally Posted by richyrich

I just don't like anything in that box in VS...

me neither, R.