RE: Long Constant Names

["Kurt Anderson" <kjanderson@xxxxxxxxxxxxx>]

>If the field really is a constant that will never change even in the
exporter, I don't see the benefit
>of export/import-const over a copy file with named constants.

You're right.  Since the use of Const in a procedure parameter means
that the recipient cannot modify the field, the keyword Const on a
variable should also mean the same thing; so it could be modified within
the module, but outside the module there is only 'read only' access to
it.

So I guess there is a difference between what I'm suggesting and what's
being suggested with a Data Structure constant.

In regard to the Data Structure constant, what I something like the
example below could be done?  So no longer is it 'S/U', it's 'Type' or
'C/S/U'.  Just brainstorming.
DayOfWeek    CDS                 Qualified

Then if you wanted to export this (for whatever reason... I guess I
personally never got into the /copy stuff), you could do:
DayOfWeek    CDS                 Qualified Export Const
(or even better, imply the keyword Const when it is a Constant Data
Structure).

Kurt