Re: Ext Print Files - In the Beginning *SPAM: 4*

I would agree that printerInd.overflow is pretty self explanatory. Thus
eliminating the need to clutter up the code with comments letting future
developers know exactly what *in21 is. Or even worse, having no
explanation of *in21 at all.

The argument I normally here is, "it is self explanitory. It is specified
on the OflInd keyword." While this is true, I still have to look around
elsewhere in the code to figure it out. This wastes time. If I see
something like:

If printerInd.overflow ;

I know exactly what is happening without wasting my time.

I'm off my soapbox now.

Brian May
Project Lead
Management Information Systems
Garan, Incorporated
Starkville, Mississippi

Young i Professionals
http://www.youngiprofessionals.com



James Perkins <jrperkinsjr@xxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
07/13/2009 11:00 AM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>


To
"RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: Ext Print Files - In the Beginning *SPAM: 4*






Brian,
I have to agree. For my overflow I generally use printerInd.overflow.
There's probably a better name than printerInd for the data structure, but
I
suppose it's much more descriptive than *IN21. :-)

--
James R. Perkins
http://twitter.com/the_jamezp


On Fri, Jul 10, 2009 at 11:56, <BMay@xxxxxxxxx> wrote:

It amazes me that almost all examples given use a *INxx indicator for

the

overflow indicator instead of defining one called something meaningful
like "overflow". Why do we continue to use cryptic numeric indicators
when we don't have to anymore?

Brian May
Project Lead
Management Information Systems
Garan, Incorporated
Starkville, Mississippi

Young i Professionals
http://www.youngiprofessionals.com
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing

list

To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.