Re: Coding Constants

Personally, I don't see the point to
d NO c 'No'
d NO c '*NO'

But I could see
d NO c 'N'
d YES c 'Y'
d NO c '0'
d YES c '1'

In which case you might consider
d FLAG_NO....
d c 'N'
d BOOLEAN_NO...
d c '0'

But I really don't like those names :)

So I might have
d NO c 'N'
d YES c 'Y'
d FALSE c '0'
d TRUE c '1'

Of course then what do you do when you need:
d FALSE c 0
d TRUE c 1
or
d FALSE c 'F'
d TRUE c 'T'

And to give you more to think about
d YESNONA_NO...
d c 'N'
d YESNONA_YES...
d c 'Y'
d YESNONA_NOT_APPLICABLE...
d c ' '

I do actually use some trinary stuff :)

Charles





On Wed, Nov 10, 2010 at 8:04 AM, Loyd Goodbar <loyd@xxxxxxxxxxxxxx> wrote:

The only real issue I see is when the same constant means different things
in different modules, such as:
d NO c 'N'
d NO c 'No'
d NO c '*NO'

I take the C-language tradition of putting the constant name in ALL CAPS.

--Loyd

On Wed, Nov 10, 2010 at 2:43 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx>wrote:

Now, when the copybooks are ready, I think they could just be added to each
module that is currently being modified. My question is, this seems so easy
and natural to do. Am I missing something?

--
This is the RPG programming on the IBM i / System i (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.