Re: Indicator enhancements (was Bale, Dan)

PC,

If a literal has that much meaning, a /copy is better, but a procedure that 
returns the value would 
be even better.  For example a procedure getdftoutq() is better than /copy 
DftOutQ C CONST('*JOB') 
is better than '*JOB'.

David Morris

>>> pcdow@yahoo.com 03/08/00 06:06PM >>>
The only thing the compiler will find is if you misspelled the name of the
named constant. It won't help if you misspelled the literal in the
definition of the named constant. Of course if you get it right once, put it
in a /COPY member, then you're getting somewhere.

From: Bale, Dan <DBale@TFSA.Textron.com>
> Excellent point!  I had not thought of that before.
>
> 'course, since I never mispell anything... ;-)
>
> (note to self: update standards)
>
> - Dan Bale

> From: Scott Mildenberger [mailto:Smildenber@Washcorp.com] 
> That creates a possibility of misspelling the literal.  That could create
> errors that can be very difficult to find.  IMO it is much better to use
the
> constants.  If you spell it incorrectly the compiler will find it.


+---
| 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
+---