|
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
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.