RE: CONST vs. VALUE

Brad,

CONST means that the procedure you are calling is not allowed to change the
parameter.  I'm not sure if this should be specified when calling system
functions or not.  If the procedure is one you have written then you will
get a compile time error if you attempt to change a parm that is defined as
CONST.  I prefer to define my parms as CONST instead of VALUE so the
compiler will tell me if I'm trying to change one.

Scott Mildenberger

> -----Original Message-----
> From: Stone, Brad V (TC) [mailto:bvstone@taylorcorp.com]
> Sent: Tuesday, March 27, 2001 9:23 AM
> To: 'RPG400-L@midrange.com'
> Subject: CONST vs. VALUE
> 
> 
> What's the difference between using CONST and VALUE on ILE 
> parm lists?  I
> have always used VALUE.  It seems to do the same thing as CONST.
> 
> ie:
>  D QCmdExc         PR                  ExtPgm('QCMDEXC')       
>  D                              256    Options(*Varsize) Const 
>  D                               15  5 Const     
> 
> Just wondering.
> 
> Brad
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to 
> RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: 
> david@midrange.com
> +---
> 
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---