RE: Subprocedure invocation

From: Jerry Adams

While debugging a programming a few minutes ago, I noticed that it had:

price = Watts;

Watts is a subprocedure and, no, there is no field name by that name.
So I meant for the line to be:

price = Watts( );

I wasn't even interested in that subprocedure, but set the debugger to
break on the line, anyway. Sure enough, it stepped right into the
subprocedure. I didn't think the program was supposed to compile, much
less invoke the subprocedure.

Nope, just a quirk of the compiler. You only need the parentheses if you
have parameters, although I think it's obvious that leaving off the parens
can be very confusing.

That's something I don't like about the .NET stuff; at least in VB.NET you
"magically" invoke the setter and getter for a field just by accessing or
updating the field itself. You can't tell just by looking at the code
whether there really is a getter or setter.

Joe