Re: Benefits of declaring literals in D-specs

One reason I like them for is for referencing an array element.

For Example, this is a program I wrote yesterday.

D Variables DS Qualified
D Points 8 0 Inz(0)
D GPA 15 4 Inz(0)
D UnitCnt 8 0 Inz(0)

D RAU DS Qualified Dim(4)
D Status LikeDS(Status) Dim(2) Inz(*LikeDS)

D Status DS Qualified
D Meas LikeDS(Variables) Dim(4) Inz(*LikeDS)

D Cmp C 1
D Reg C 2
D Ara C 3
D Unt C 4

D All C 1
D Core C 2

D CP C 1
D R90 C 2
D YTD C 3
D RYTD C 4

/Free

// When looking at this, it means more than the alternative.
RAU(Ara).Status(All).Meas(CP).Points +=
RAU(Unt).Status(All).Meas(CP).Points;

// alternative.
RAU(3).Status(1).Meas(1).Points +=
RAU(4).Status(1).Meas(1).Points;

/End-Free




Michael Schutte
Admin Professional
Bob Evans Farms, Inc.
Big Farm Salads - Hurry in to enjoy the newest farm-fresh taste from Bob
Evans, the "Home of Homestyle."


rpg400-l-bounces@xxxxxxxxxxxx wrote on 05/03/2007 09:05:01 AM:

We are in the process of revamping our coding standards. Eons ago (and I
still see it today) I saw a few presenters declare all literals in the
D-specs. One presenter explained why he liked declaring literals this

way,

though I don't remember the reasons given. Now I have been asked to

compile

a list of reasons/benefits for declaring literals in the D-specs. If

there

are some real benefits to declaring literals this way, then we will make

it

part of our standards. If you would be so kind to share your thoughts, I
would appreciate it.

Kent Hohlen
Eagle Window & Door
--
This is the RPG programming on the AS400 / 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.