Re: Who the bloody eff still codes CABEQ in this century?!?!?!?

On Mon, Jul 24, 2017 at 12:46 PM, Dan <dan27649@xxxxxxxxx> wrote:

Speaking of the venerated GOTO, I found this in the RPG reference:

Use a GOTO operation to specify a branch:
- From a detail calculation line to another detail calculation line
- From a total calculation line to another total calculation line
- From a detail calculation line to a total calculation line
- From a subroutine to a TAG or ENDSR within the same subroutine
- From a subroutine to a detail calculation line or to a total

calculation line.

This kind of thing really accentuates the similarity between RPG and
assembly. A branch is a branch. There is minimal enforcement of
structure. Visually and conceptually, I always found the "factor1,
opcode, factor2, result" columns reminiscent of typical assembly
language:

<https://en.wikipedia.org/wiki/Assembly_language#/media/File:Motorola_6800_Assembly_Language.png>

The CABxx opcodes (which started this thread) are also lifted straight
out of assembly.

At my first job, we did have a form of code review. In one case I will
never forget, my manager/mentor told me "oh, you can handle this bit
of logic simply by using GOTO to here" as he proceeded to scrawl a tag
inside an ELSE "block" to serve as a target from outside of that ELSE
block. He said my attempt to make it more structured was acceptable,
though needlessly complicated.

I was mortified. I hoped he was joking, but he wasn't.

John Y.