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

message: 3
date: Thu, 20 Jul 2017 16:07:54 -0400
from: Dan <dan27649@xxxxxxxxx>
subject: Re: Who the bloody eff still codes CABEQ in this century?!?!?!?

I like both Scott's and Jon's ideas for "customizing" the compiler.

The problem, of course, is all of the legacy code. No one's gonna buy the

idea that if I need to make a one-line change to a program that I first have
to gut it of all the CAB*, CAS*, GOTO, and TAG opcodes.

I could see a process that wouldn't need IBM's blessing that removes all

authority to the RPG compiler commands except to a restricted profile, and
force compiles to go through a pre-processor that does the vetting. Again,
with the legacy code issue, if you had a SCM tool, you could set a base for
existing members and not allow any new uses of "banned" opcodes. Frankly,
though, if developers and code reviewers can't discipline themselves to
adhere to coding standards, there are other problems that need to be
addressed.

- Dan

I like this idea Dan. I would add to your list a plan END (where it should
be ENDIF, ENDDO....). At least generate a report of these violations, we
have a lot of code written in fixed RPGIV format with this crap in it. I
don't want to have to rewrite the code every time I need to make a small
fix, so it should compile and run. I am in a one man shop (as far as the IBM
I goes), but I get it. Everywhere that I have been, I have encountered a lot
of code written by predecessors that contains code written as if they were
writing RPGII on a System 36 (and no, I never had that pleasure).

Jim