You won't win the battle trying to fight it this way...

RPG III is ideal for cryptic hard to maintain code...

Try changing the fight

show somebody the MOVEA line of code and ask what affect on the program it
has..

Of course they won't be able to tell you, without looking to see what
indicators 30, 31, 32 are used for.

Now show them one of the RPG IV options with a decently named indicator
group and ask them to explain it.

Have them imagine which is going to be easier to come back to maintain
after 6months...

Charles

On Tue, Jan 22, 2013 at 10:43 AM, Buzz Fenner <bfenner@xxxxxxxxxxxxxxxx>wrote:

To summarize (and to provide some background) I was faced with the
following
coding style during a modification to some RPG III code:

C MOVEA'101' *IN,30

This has been used extensively in my shop for the last 30 years. I'm trying
to show the other guys the advantages of /Free but I wasn't able to do the
same thing with just a single line of code. Posting the problem to the
forum
helped me a lot, and it also garnered the usual comments about bad coding
techniques. I'll give you that, but I'm in a bit of an ideological war here
and unless I can reproduce the same results using a single line of code,
I'll lose this battle. So much for background...



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.