Re: Question about prototyping

Matt (and everyone else)- my terminology (prototype vs procedure) was
confusing - my apologies. I'm seeing the procedures at the bottom, with
the prototypes where they belong - in the D specs.

"For example, if I write a service program, I'll put all of the prototypes
for the exposed procedures in a copy book along with any constants and/or
data structures that calling programs will need to use it. Both the
service program and the calling program will then import the same copy
book."

Yes - I do that too.

"But I assume the idea behind it is the same, instead of having a
seperate copy member you just have the one member with compiler
directives that control rather of not only the prototypes are seen."

Yes Charles - that is how I approach them too. And the concept of
modularity was more in line with my thinking (than was privatization -
which now is something we will also consider).

Adam said:

"The fact that procedures can be (and should be, where possible) written
so they have no side effects leads to IMO the biggest benefit of
procedures over subroutines. Maintenance is a lot simpler if you can just
look at the CALLP line and determine whether the variables you are
interested in are used or changed by the procedure. With subroutines, you
have look at the subroutine code and determine which variables are updated
and which key lists are used before you can confidently change any of the
code surrounding the EXSR. "

That is the kind of answer I was looking for as this question arose from a
co-worker who is reviewing some code written by a vendor and she was
unfamiliar with the practice. The only answer I could offer was the
subroutine analogy, but Adam provided a much better elaboration.

Vern: "I've not tested whether a prototype declared within a procedure is
usable outside of that procedure, I suspect not."

I suspect that is true too Vern.

Thanks to all of you for clarifying - I just had my coworker read all of
your responses.

Your input is truly appreciated.

Regards, Jerry

Gerald Kern - MIS Project Leader
Lotus Notes/Domino Administrator
IBM Certified RPG IV Developer
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623-4299
Phone 419-479-5535
gkern@xxxxxxxxxxxxxxxx


This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential and privileged
information. Any unauthorized use, disclosure or distribution is
prohibited. If you are not the intended recipient, please inform the
sender by reply e-mail and destroy this and all copies of this message.