RE: Naming Conventions (was RE: Subroutines vs Subprocedures (was RE: Indicators))

Actually, I wasn't talking about using the PREFIX keyword on the DS
subfields.

Instead, something like:

d t_RtnDta       ds             qualified based(dummyPtr)
d  field1               19a
d  field2               10a


d myRtnDta1                     likeds(t_RtnDta)
d myRtnDta2                             likeds(t_RtnDta)


What I was talking about is the "t_" prefix on, just something to get across
the idea that the t_RtnDta is a "template" intended to be used in a LIKEDS
and not actually used for storage.


Comments?

Charles



> -----Original Message-----
> From: Barbara Morris [mailto:bmorris@xxxxxxxxxx]
> Sent: Thursday, August 26, 2004 9:53 PM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: Re: Naming Conventions (was RE: Subroutines vs 
> Subprocedures (wasRE: Indicators))
> 
> 
> CWilt@xxxxxxxxxxxx wrote:
> > ...
> > Speaking of qualified DS'es, I was tossing around the idea 
> of a prefix for
> > template DS'es.  In other words, a DS that is not intended 
> to actually be
> > used except in the LIKEDS keyword.
> > 
> 
> If you use QUALIFIED to define the template, you don't really need the
> prefix.  If you do use a prefix, the prefix will carry over to all the
> LIKEDS data structures; you'll have to type it when you use every
> subfield of every LIKEDS data structure. DS1.PFX_FLD1, 
> DS2.PFX_FLD1 ...
> 
> --
> 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.
>