For external procedures/programs I keep a governance document that lists, among other things, the interface (parameters). When I want to use one of these, I reference the governance document and code from that. That is, the prototype is in a /Copy member, but now I know that the attributes of the fields that I need to pass back and forth. I admit that I built the list because I could never remember the names of the procedures/programs that performed functions that I knew I had written, but the other stuff comes in handy, too. Got it (the idea) from a session that Trevor gave.
Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
All I know is that we lost the game. What's so historic about that? -Harvey Haddix after pitching 12 perfect innings and losing 1-0 in the thirteenth.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Rory Hewitt
Sent: Friday, May 14, 2010 10:30 AM
To: RPG programming on the IBM i / System i
Subject: Re: Parameter prototype question
David,
One could take the approach that *all* parameter check has to be done
manually, whether or not CONST or VALUE has been specified. For instance (to
take one of my procedures I've been working on), if you have a procedure
that can accept a 3-character code, representing a record type to process
('HDR', 'DTL', OPT' etc.), then any time you call that procedure (especially
if you haven't used it for a while) you might have to check to see what the
valid record types are. Certainly a programmer who's never called that
procedure would have to do so.
In many cases, you have to know what the meanings are of different parameter
values. The same applies (or should apply) to parameter value limits.
Rory
On Fri, May 14, 2010 at 7:44 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx>wrote:
Today I learned that protoyped procedure parameter checking must be done
manually when using CONST or VALUE.
Thanks.
midrange.com
