×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
David,
That is generally what I personally try to do. A copy book for constants
that are used everywhere and others are always global constants, unless
there is no reason any other procedure would EVER need to use it.
I prefer RELATION_AUNT to just AUNT. While AUNT would work fine in this
instance, sometimes you might want use the same word for other constants.
Take ERROR for example, you might have an ORDER_ERROR, ORDER_LINE_ERROR,
etc. The more descriptive the better in my opinion.
Just to let you know how I generally code my constants. For any constant
that I use for general constants I always us a C_ as a prefix, e.g
C_RELATION_AUNT. For IBM style, *ALL, I use an @, @ALL. I use these because
RPG is not case sensitive so it just signifies that the field is a constant
on not a normal variable.
--
James R. Perkins
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: Constants in RPG - what would you do?, (continued)
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.