Re: Subprocedure invocation

On 09/01/2008, at 8:08 AM, Jerry Adams wrote:

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.

Always been that way. In fact on earlier releases empty parentheses were not allowed and would cause a compile failure. This was relaxed some time ago (I think VRM510). Always better practice to use the empty parentheses to SHOW a procedure call rather than a variable assignment.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------