Re: Prototype definition enforcement

+1

:--)

Did the problem arise for an exported procedure called by another

module?

I created RFE 117030 to address that problem.

https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=117030

Briefly described the problem is that the compiler does not enforce a
prototype for exported procedures. That can lead to a situation where

the

procedure interface does not match the prototype (stored in a /copy

member)

and where a caller, that relies on the prototype, passes the wrong
parameters to the procedure.

It is really nice that we no longer have to include the prototype for
private procedures. But for exported procedures (Keyword: "export") the
compiler MUST enforce the presence of a prototype.

Just my 2 cents.

Thomas.

<br />
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else is
unauthorized. If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it, is
prohibited and may be unlawful.