Hi Dieter,
my understanding is that the compiler checked the protytpe against the procedure interface before 7.1. With 6.1 or lower all procedures needed to have a prototype and of course we have our external prototypes in a /copy member. This way all protypes were checked against the procedure interfaces.
And yes, it was a bit annoying to create prototypes for internal procedures. But now, the compiler is too lax.
Thomas.
-----Ursprüngliche Nachricht-----
Von: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im Auftrag von D*B
Gesendet: Dienstag, 20. Februar 2018 07:03
An: RPG programming on the IBM i / System i
Betreff: Re: 7.1 and RPG prototypes
<Thomas>
is there an option to enforce prototypes for exported procedures on 7.1+?
</Thomas>
Hi Thomas,
it wouldn't be too hard, to check this (and other things) in a preprocessor (plug-in), but the real gap to have consistence between caller and callee isn't closed by this. The real problem, needing enhancements is, to check the caller prototype against the procedure interface of the callee, as other non as400 compilers are doing.
Dieter
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone else is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender.
midrange.com
