Re: Why RNF5410 for undefined variable in prototype call?

On 21/04/2010, at 8:32 AM, Rory Hewitt wrote:

It's *very* weird that using an undefined procedure (e.g. RUNCMD) doesn't
throw RNF5410... It kinda throws your 'some logic' out the window...<grin>.

Confusing a compiler is a bit like teasing stupid people--not difficult but rapidly loses its appeal. They both have a very simple view of the world and if something doesn't fit the preconceived rules confusion abounds.

I expect that lack of RNF5410 for RUNCMD is because it's already been flagged as an undefined name thus limited further parsing occurs on it. You get the "Name undefined" and then "Undefined name used in expression" standard errors. The compiler never examines the expression to determine that it's a function call thus no prototype errors are shown. The errors it does show are good enough to resolve the problem so ...

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 / \
--------------------------------------------------------------------