Can someone explain this use of "new"?

[CMirandaman]

I have another newbie question I could use some help with. I ran across this
code in one of the MS training guides:

public class NullTokenVisito r
{...}

public class Application
{
public static void Main()
{
new NullTokenVisito r();
}

}
I was surprised that this code compiles and runs. It appears that I am
creating a new instance of the NullTokenVisito r class without assigning the
object reference to a variable. Am I understanding this code correctly? If
so, what would be the purpose of using this type of expression outside of a
purely academic exercises?

[Ashura]

the only thing matters to the compiler is syntax (c#).
theres *nothing* wrong to that code.

[Steven Nagy]

It would mean that any code in the NullTokenVisito r's constructor will
be called. Perhaps the code in that constructor has some affect on
objects outside of its scope. Maybe it "adds 1" to the "Visitor" table
in a database or something. God knows really... whats in the
constructor code?

Its kind of along the same lines as something like this:
Dim d as double = 45.7214
Math.Floor(d)

I can call Math.Floor(d) and not assign its result to anything. It
would be pointless, but the compiler accepts it, and still performs the
flooring function....

This help?

I could be wrong tho... (I usually rate my chances at around 25%
correctness)

[Peter N Roth]

Does that mean you're overpaid by a factor of 4? ;o)
--
Grace + Peace,
Peter N Roth
Engineering Objects International
http://engineeringobjects.com
Home of Matrix.NET
"Steven Nagy" <le*********@ho tmail.com> wrote in message
news:11******** **************@ g43g2000cwa.goo glegroups.com.. .
[ ]

I could be wrong tho... (I usually rate my chances at around 25%
correctness)

[Steven Nagy]

At my pay rate, I'm practically a volunteer...

[CMirandaman]

Steven,

Thanks for your input. In the example you provide of Math.Floor() I sort of
assumed that Floor is a static method so it makes sense that you would call
it without instantiating an object. What good is it to fire the constructor
in a class if you don't assigne the object reference to a variable? The
object is lost and now just wasted memory. It bakes my noodle is that the C#
compiler would even allow me to instantiate an object without assigning it to
a variable. The sample code I provided uses it as an artifical test just to
make sure that the class would instantiate without throwing an error. I
wouldn't expect to ever leave that sort of code in a release application and
I can't figure out what sort of practical use such a statement could have in
a live application.

"Steven Nagy" wrote:

It would mean that any code in the NullTokenVisito r's constructor will
be called. Perhaps the code in that constructor has some affect on
objects outside of its scope. Maybe it "adds 1" to the "Visitor" table
in a database or something. God knows really... whats in the
constructor code?

Its kind of along the same lines as something like this:
Dim d as double = 45.7214
Math.Floor(d)

I can call Math.Floor(d) and not assign its result to anything. It
would be pointless, but the compiler accepts it, and still performs the
flooring function....

This help?

I could be wrong tho... (I usually rate my chances at around 25%
correctness)

[Marc Gravell]

Why?

Firstly, the object isn't lost: the GC knows exactly where to find it, and
will come a-knockin' very soon.

Secondly, the compiler has no way of knowing what your ctor does; it could
increment static variables, it could chhose to throw an exception (perhaps
arguably unwisely, but that's another issue), it could choose to tweak any
of the variables in the arguments to the ctor.

Thridly - in the "lost" scenario, your instance ctor could also perhaps (not
100% sure - haven't tried it) add itself to a static collection, so even
less "lost" - in fact, if it was a form, the ctor could also perhaps show
itself? (again not tried, and again, not perhaps adviseable).

OK, fine, all of the above scenarios would be better done in better ways,
but I see no sensible reason that the compiler should know this. I'd rather
it simply collected an object occasionally than have me wondering why
something that looks logical doesn't work...

Marc

[Steven Nagy]

Exactly.

The point is you can do it, just like you code like this:

MyObject.x = 1;
MyObject.x = 2;
MyObject.x = 1;

Seems completely pointless! But the compiler lets you do it...
And it could be that the X property is doing more than what the code
suggests... it could be launching missiles at the soviet union in the
related property getter.