Did the problem arise for an exported procedure called by another
I created RFE 117030 to address that problem.


Briefly described the problem is that the compiler does not enforce a
prototype for exported procedures. That can lead to a situation where
procedure interface does not match the prototype (stored in a /copy
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.

<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.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].