RE: Define field as an indicator in D-specs

That's fine when checking the status but somewhere in the code you have to
set it's value. Then you need *ON, *OFF, true, false, 1, 0 ........




From:
"Briggs, Trevor (TBriggs2)" <TBriggs2@xxxxxxxxxxx>
To:
<rpg400-l@xxxxxxxxxxxx>,
Date:
12/06/2013 12:27 PM
Subject:
RE: Define field as an indicator in D-specs
Sent by:
rpg400-l-bounces@xxxxxxxxxxxx



Again, if you name the variable correctly you don't need to use either.

Why write:
If ValidIndicator = True;

When you could write:
If ValueIsValid;

Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Englander, Douglas
Sent: Friday, December 06, 2013 1:16 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Define field as an indicator in D-specs


I'm not confused. I don't understand why someone would want to write
more code than they have to.

If people steeped in other languages can't figure out what is meant by
*ON and *OFF, then we, as developers, have bigger issues.

Maybe we should ask IBM to include *TRUE and *FALSE as additional ways
to signify *ON and *OFF.