AW: passing parameters longer than expected

Hi,

that's why I always insist to use reference files, variables or data
structures that are included as templates in the prototype definition.
All variables, data structures, data structure subfields and parameters must
be defined based on this templates.
If a reference variable must be changed the only thing you have to do is to
recompile everything where this variable is used.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Dave
Gesendet: Friday, 23. March 2012 12:23
An: RPG programming on the IBM i / System i
Betreff: passing parameters longer than expected

Hi, all,
I think this subject has been well debated in the past, but I just got
bitten again and would like to know how to protect myself in the
future. I copied and adapted some code and did not realise until well
into testing that I was passing a 100A parameter to a procedure
expecting 45A. I believe that when CONST is specified, the compiler
converts the parameter and there is no warning. I'm still wondering
why as I think that prototyping was introduced in order to protect one
against this sort of error. Now I discover that many other procedures
are doing the same call and I have to analyze to see if I can just go
ahead and change the 45A parameter to 100A