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

That's the beauty of something like an exit program -- you can write any logic you want.

So if you want to allow it in old programs but not new ones, you could, for example, have a database of old programs where it's allowed, and the exit program could query that to decide what to allow and deny. (Or any other way you decide to do it... since the logic is up to you.)

Using flags would not provide that level of configurability.



On 7/20/2017 4:47 PM, Charles Wilt wrote:

The problem I have with either the exit program or compiler flags...

Is that I'd imagine most shops are like ours. I may not allow new line
code that uses a GOTO, but I'm not going to force existing ones to be
removed just because the developer is in there changing some other line.

Sure, I'd like too...but that's just not going to happen.

Our standards review is done base upon the output of of DIFF when code is
checked into SVN.

AFAIK, it's a manual review...It'd be nice for a SVN/GIT module that your
could configure to flag certain things.

Charles



On Thu, Jul 20, 2017 at 3:21 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

Scott's approach works for me and certainly would reduce the amount of
work IBM needs to do - in theory at least.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jul 20, 2017, at 2:41 PM, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>

wrote:

Maybe the thing IBM should do is add an exit point. During compile, the

RPG compiler could call any registered exit programs and pass the opcodes
to it while checking the source.

Customers like us could then write code to enforce rules like "never use

CABEQ" or "never use MOVE" or "no gotos allowed" or whatever a shop wants
to do.

On 7/19/2017 2:33 PM, Dan wrote:

What are the chances we could get IBM / Barbara to get the compiler to

puke

on any of the CAB* opcodes?

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (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.

Please contact support@xxxxxxxxxxxx for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link: http://amzn.to/2dEadiD

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD