Re: Why are DCL statements restricted to where appear

Personally I’m happy that it doesn’t - it would just take us back to the bad old days of result field definitions.

This is an assumption on my part but my guess as to why the limit exists is that RPG still basically requires its specs in sequence. The only requirement that was really relaxed is the ability to intermix F and D specs. Since these are both replaced by DCLs it makes sense for those DCLs to be able to be interleaved. In fact, as a result, you can now also intermix “real” F and D specs.

And of course they can be specified in subprocedures.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Oct 8, 2014, at 2:50 PM, Chris Holko <cholko@xxxxxxxxxxxxxx> wrote:

Not sure if this is an appropriate question for the list , however I am curious why DCL specs cannot appear anywhere within the source as long as they appear before they variable is used

Sent from my iPhone
--
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.