Re: Question about prototyping

Charles Wilt wrote:
Adam Glauser wrote:

Also, just to be clear, it would be the prototype in the copybook, not
the procedure. Your instinct is right however. If the code is reusable
within a single program, there is a good chance it can be reused in
other programs as well.

>

If the procedure is "private" and thus only used within the module,
then I leave the prototype in the module as well.

It doesn't make sense to me to put the prototype in a copy book when
the procedure can't be used by anybody else.

Yes, me too. I didn't mean to suggest that prototypes for "private" procs should be in copybooks, though I see how it could read that way. I meant that procedures should _not_ go in copybooks.

Most of my private procedures exist to provide modularity with defined
interfaces to the code. Not for reusability.

That is a (much!) more succinct way to say what I was trying to say. :)