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

"Are you saying you can keep the legacy GOTO, add new free-form code, and NOT use /free and /end-free?"

Sadly true.

One of the downsides of getting rid of the /free tyranny was that the fixed form can now be freely intermixed with free-form.

Luckily most of the dinosaurs don't read magazine articles or forums like this so shhhhhhh ... don't tell 'em and they've never notice.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jul 19, 2017, at 5:25 PM, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:

On Wed, Jul 19, 2017 at 5:14 PM, Dan <dan27649@xxxxxxxxx> wrote:

Any new code I add to existing programs is free-format, and it's not
unusual that a GOTO is required in the middle of it because of the way the
rest of the code is architected. I'm just glad we don't need the /free &
/end-free directives any longer, cuz that would be really ugly.

Are you saying you can keep the legacy GOTO, add new free-form code,
and NOT use /free and /end-free?

If you're talking about moving the GOTO and tags to /copy members,
well, to me that's more-or-less just as ugly as /free and /end-free.

John Y.
--
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