Re: worst RPG ever seen?

[Jerry Adams <jerry@xxxxxxxxxxxxxxx>]

I think it's very hard to run out of indicators.  Like Booth, when I 
started (S/3), we too were taught to assign a unique indicator to each 
"purpose."  I don't recall actually running out of indicators, but I do 
recall forgetting what each one did.


Later (still on a /3) when I had an epiphany that uniqueness wasn't 
important (except in the I-specs and even that could be shortened), I 
wrote a 2000+ line program with only one [1] indicator (aside from the 
aforementioned I-specs).


OK, then, my candidate.  Bear in mind that I wrote this and that it was 
my very first program.

C   64         GOTO   END

CL5      END   TAG


That sucker ran through lunch on one invoice before we killed it.  
That's when I went back and memorized the RPG cycle.


        * Jerry C. Adams
*iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
        615.995.7024
fax
        615.995.1201
email
        jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



James H H Lampert wrote:

> It's not exactly all that hard to run out of indicators, 
> particularly in OPM. Sometimes, if a program has lots and 
> lots of Boolean data, I have to (1) check compilation 
> listings to find unused indicators, and/or (2) ration the 
> indicators, and only use them for those Boolean values 
> that, for one reason or another (like display file 
> control), HAVE to be indicators.
>
> Personally, I'm rather fond of using multiples of 13 to 
> indicate that something bad happened, and multiples of 7 
> to indicate that something good happened.
>
> --
> JHHL
>