RE: dRE: No Subroutines (was Re: Debugging many subprocedures)

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

> John's code snippet is a perfect example of a procedure imitating a
> subroutine. I personally would never do a validation subroutine as a
> procedure, there is no advantage. Nothing is declared locally to the
> procedure, all variables are global to the module.

How do you separate your business logic from your display logic, then? 
How to you write your business logic (and by all accounts, validation is 
business logic!) so that it can be re-used from both your GUI display and 
your green screen?

> If I have three procedures in a module and they each have to validate parms,
> then all of the parms to those procedures have to be global, or I can pass
> the parms to the validate procedures, or I can use 3 subroutines within the
> scope of the respective procedures to validate its parms locally. So a
> subroutine becomes sub-sub procedure local to it's parent sub procedure.

Which fields do you validate in each subprocedure?  How do you determine 
that?

Is there a reason you need to validate more than one field, or a set of 
related fields, in a single subprocedure?