× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Are indicators evil creatures or victims of poor shop standar ds?
  • From: "Jim" <jcannon@xxxxxxxxxxx>
  • Date: Tue, 7 Mar 2000 15:49:52 -0700

EXCEPT in the case where you might SETON and indicator. It 
remains ON until you SETOF the indicator, or end the program.



From:                   Joel Fritz <JFritz@sharperimage.com>
To:                     "'RPG400-L@midrange.com'" <RPG400-L@midrange.com>
Subject:                RE: Are indicators evil creatures or victims of poor 
shop standar
        ds?
Date sent:              Tue, 7 Mar 2000 13:46:29 -0800 
Send reply to:          RPG400-L@midrange.com

This is like our shop standard--never assume a result indicator retains its
value more than one line of code after it's set.  If you need its value
somewhere else, the line of code that follows the line of code that sets the
indicator sets a flag based on the indicator value.

(Last line of a read loop by, our definition, comes before the loop control
statement.)

> -----Original Message-----
> From: James W. Kilgore [mailto:qappdsn@attglobal.net]
> Sent: Tuesday, March 07, 2000 12:03 PM
> To: RPG400-L@midrange.com
> Subject: Re: Are indicators evil creatures or victims of poor shop
> standards?
> 
> 
> Buck,
> 
> I agree that indicators are not -evil-, just a pain.
> 
> Since we must us indicators for such things as position 
> cursor for a display
> file, they live on.
> 
> We have strong shop standards and have not found indicators 
> to be a particular
> problem.  Our standard is that a given indicator has a 
> particular meaning or a
> set of rules.  The only reason it works is through enforced 
> uniformity.
> 
> Here's a small example: Every file in the application has a 
> 'get record' routine
> that does a CHAIN.  Since we have to support V3R2 RPGIII, 
> this routine is in a
> /COPY member.  Every, and I mean every, incarnation of this 
> routine uses *IN90 as
> the resulting indicator.
> 
> These routines then uses *IN90 to set flags (variables) that 
> are used within the
> mainline code.  The rule for *IN90 is that it's use never 
> goes beyond the
> immediate purpose, flags are set instead.
> 
> You're right, without a plan, indicators are a mess.
> 
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.