RE: Setting off multiple indicators

["Peter Colpaert" <Peter.Colpaert@xxxxxxxxxxxx>]

I second that.

As long as we're forced to use *INxx in our display and printer files, I
for one like it when the same indicator can be easily found in the source.

Call me old-fashioned, but that's how I prefer to work.

Now get your flame throwers ready <ducking>.

Peter Colpaert
Application Developer

Honda Europe NV
Langerbruggestraat 104
B-9000 GENT
Belgium
Peter.Colpaert@honda-eu.com
Tel: +32 9 2501 334
Fax: +32 9 2501 231
----------
Yoda of Borg are we: Futile is resistance. Assimilate you, we will.
----------




"Lance Gillespie" <lgillespie@cvwd.org>@midrange.com on 18/11/2002 16:59:52
Please respond to rpg400-l@midrange.com
Sent by:  rpg400-l-admin@midrange.com

To:   <rpg400-l@midrange.com>

cc:

Subject:  RE: Setting off multiple indicators


I agree with everyone about block seton, setoff - don't do it.

However, I am going to commit heresy and say that I am not
in favor of using smoke, mirrors, misdirection, obscure pointer
tricks, or any of the other 'cool' indicator tricks people advocate
for displays - and here is why:  In the DDS for the screen,
the programmer has to use indicators by number.  When you
are looking at the code trying to debug it, you see that IN30
does this and IN52 does this and IN03 means they pressed
F3 and IN60 display the error message and so on.  So off
you go to the code to see where these are set on and off.
OH NOOOOO!  The previous programer had a subscription
to Midrange Computing!  So in this program there is pointer
redirection to an externally described data structure with
names for the indicators, in that program pointers are used
to map the *in array to another array overlain with a
data structure with names, the third program does all
that and uses the AID byte.  Hours later, you finally finish
hand diagraming where IN30 is turned on.
If DDS allowed named indicators, then named indicators
would be the way to go, but as long DDS requires
numbered indicators, I would rather see the same
references used in the program.

Now let's see if we can't beat the 'os/400 commands
are easier to use than unix' flame war!







Lance Gillespie
Coachella Valley Water District
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.






______________________________________________________________________
The information contained in this communication is confidential and may be
legally privileged. It is intended solely for the use of the individual or
the entity to whom it is addressed and others authorised to receive it. If
you have received it by mistake, please let the sender know by e-mail reply
and delete it from your system.
If you are not the intended recipient you are hereby notified that any
disclosure, copying, distribution or taking any action in reliance of the
contents of this information is strictly prohibited and may be unlawful.
Honda Europe NV is neither liable for the proper and complete transmission
of the information contained in this communication nor for any delay in its
receipt.