Re: Long Constant Names

[Tony Carolla <carolla@xxxxxxxxx>]

I use constant fields for a few things, commands strings I intend to
use for system() commands, and all literals I intend to use and not
modify at runtime.

What I was asking for was the ability to create a data structure, with
certain elements that remained constant. i.e.

     D FN              DS                  Qualified
     D  Acro                          3A   Inz(*Blanks)
     D  Chunk                              Const('FILES/DOCTRL3')

The second component of the data structure should never change.  In my
mind, it should be declared constant.


On Tue, 04 Jan 2005 13:13:10 -0500, Barbara Morris <bmorris@xxxxxxxxxx> wrote:
> Tony Carolla wrote:
> >
> > When you say users wanted to allow CONST for variables, that can be
> > inz'd but not modified, isn't this the definition of a Constant.  If
> > you specify a 'C', and use the CONST keyword, voila.  You have
> > initialized a variable that can't be modified.
> >
> > By variable, are you referring to using it in a Data Struct?
> >
> 
> Yep, you're right that constant standalone fields wouldn't be that
> useful except possibly for arrays (I guess they would be initialized
> through CTDATA or FROMFILE or maybe (WACI) there would be some keyword
> to allow update in the *INZSR).
> 
> --
> 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.
> 
> 


-- 
"Enter any 11-digit prime number to continue..."