RE: Long Constant Names

What about using Const on a variable for the purpose of exporting a
variable that cannot be changed by other programs.  That way when you
define the field for importing, you don't have to type in the value, so
the field really is a constant, but it's use is to minimize duplication
of (hard)coding between modules.

Though it doesn't seem that this functionality (and the coding style
that goes with it) is all that popular.  But it seems to me like a small
step toward creating something that could potentially be comparable to a
class in an OO language.

 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
Sent: Tuesday, January 04, 2005 12:13 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Long Constant Names

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.