Re: Question about legacy coding style

I remember being new to RPG and sitting down with a pencil and paper
to figure out what MULT 100.0001 was doing....

I remember thing it was a neat trick...then a couple years later ran
across a rant about it included a description of the hoops it required
the CPU to jump through....

I started replacing them as I found them...

Charles

On Thu, Mar 24, 2011 at 8:35 AM, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote:

On 3/24/2011 4:51 AM, Craig Pelkie wrote:

Thanks for all of the replies.

This type of thing always strikes me as being "programming archeology", in
that you had to be there to really know why something was done (what it is
doing is not too hard to discern, but the "why's" become dimmer over time).

There should probably be some project launched as a wiki to collect and
document these kinds of idioms. Somebody 10 years from now won't have any
idea why this was done, and those who remember, well, they might not be on
this list. Legacy COBOL is probably the same way (to pick another widely
used language with an enormous legacy code base).

Absolutely.  MULT 100.0001 has to go in there!  I can't imagine anybody
but an (old) RPG programmer being able to decipher that one.

I have a couple of old 8085 assembler tricks rattling around in my head
as well <grin>.

Joe
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.