Re: Why RNF5410 for undefined variable in prototype call?

[Rory Hewitt <rory.hewitt@xxxxxxxxx>]

Simon,

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>.
As you say, it's an 'expected partner' error message, and can be ignored.

Rory

On Tue, Apr 20, 2010 at 3:14 PM, Simon Coulter <shc@xxxxxxxxxxxxxxxxx>wrote:

> [...] Note also that for RUNCMD the compiler knows
> the name is not defined but doesn't issue RNF5410 even though a
> prototype does not exist.
>
> However I can see some logic to the current behaviour. If any of the
> parameters are undefined then the call is undefined and therefore the
> associated prototype is also undefined.
>
> Should we care? I've always ignored this message and just treated it
> as an expected partner of the RNF7503 error. Just be grateful the RPG
> compiler doesn't get as completely hosed as the C compiler when it
> encounters syntax errors. At least it can regroup and recover to give
> sensible error messages for the remaining code whereas the C compiler
> frequently just disappears down the sewer and spews out misleading and
> erroneous messages for so-called 'problems' after the first error.
>
>
> Regards,
> Simon Coulter.