Re: Need some ammunition (Procedures vs. Sub-routines)

On 1/6/2014 6:04 PM, Scott Klement wrote:

I'm probably about to make a stupid comment, but... you're doing far
more than is necessary to make this into a service program.

Alot of what you're changing is done because you're converting this from
a main procedure into a subprocedure. That's technically not necessary
to make it into a service program. You can still use *ENTRY PLIST with
a service program. You can still use the cycle to open/close files and
call *INZSR with a service program.

Granted, what you're doing is a good idea... and is a best practice.

All your points are spot on.

The OP's situation seems to be that his colleagues are not at all
familiar with subprocedures; they are novices. Novices want - they need
- a framework of simple rules they can follow. I was hoping to get the
novices a more or less real world implementation and show them that it's
not that scary.

Soon enough, they'll be debating about whether to put the display panel
attribute constants in a separate /copy member. And that'll be a good
thing, because then we'll have more thoughtful programmers in the community.
--buck