RE: Formal RPG Free Standards

If your calling a different program you don't have to write a PI. If that
program has the old input parms it will still work. You need the PR, but
that should be in a copy member so you only create it that once. and don't
have to make it over and over. If I understand correctly at 7.1? you don't
have to make a PR for internal procedures.




From:
"Jack Tucky" <jacktucky@xxxxxxxxx>
To:
"'RPG programming on the IBM i / System i'" <rpg400-l@xxxxxxxxxxxx>,
Date:
09/10/2012 01:40 PM
Subject:
RE: Formal RPG Free Standards
Sent by:
rpg400-l-bounces@xxxxxxxxxxxx



Is there a way to do a call without defining the PR and PI?

When converting code to free form I tend to leave the CALL's with PARM's
in
column format.

Thanks.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Joep Beckeringh
Sent: Sunday, September 09, 2012 6:17 PM
To: RPG programming on the IBM i / System i
Subject: Re: Formal RPG Free Standards

Hi Scott,

Another thing I found that can't be done in fixed format: use XML-INTO
with error extender. It just doesn't fit!

Joep Beckeringh


Op 08-09-12 07:11, Scott Klement schreef:

Hi John,

I understand how you made the mistake.

FWIW -- there are _very_ few things that can be done in free format that
you can't also do in fixed format. (in almost the exact same way!)

The big advantages to free format are:

1) The ability to indent code (since opcodes, factor1/factor2/result,
etc) don't have to be in particular positions.

2) More space, since you don't waste about 1/2 of each line of code with
unnecessarily blanks. This is the BIGGIE for me... having space to
write things. It was so hard to make expressions fit in the "extended
factor 2" syntax, since you were so limited in space.

The advantage is NOT functionality. Aside from the %FIELDS BIF, I can't
think of anything that you can code in free-format that doesn't also
work in fixed.