Re: Impossible to even think about rewriting in RPG

On 2011/6/30 9:15 AM, Bob P. Roche wrote:

While I agree it is best practice and should be done. It is not a NEED to
put prototypes in a /copy file. The system doesn't force you to do it that
way.

If you mean that you can just code the prototype into each source member that needs it, that way lies madness.

I always say that there should be exactly one prototype for each program or procedure.
- in the same source member for something that isn't called from another RPG module
- in a /copy file for something that is called from another RPG module

In 7.1, even if you don't code a prototype, you still have one prototype, but it is generated implicitly by the compiler. So if you were naughty and omitted the prototype from the module containing the program, and coded the prototype in another module calling the program, you'd still be breaking the rule because you'd have one coded prototype in the caller, plus one implicit prototype generated by the compiler.