> 3. Best bet: avoid literals. I never code them. Bet you can > always find a way around coding a literal; e.g., in the > example above: > > LARL 3,h23 > > H23 dc h'23' > > -Steve Comstock > The Trainer's Friend, Inc.>
I am all for constants like... SEC_HOUR DC F'3600' But your example of a constant named 'H23' is something I would definitly not recommend. After 10 years of of updates the programs will be riddled with constants like: H23 DC H'22' NLG DC C'EUR' Use constants with an appropriate name if the literal isn't just a literal but has some functional meaning. Use literals for, well, literals. Fred! ----------------------------------------------------------------- ATTENTION: The information in this electronic mail message is private and confidential, and only intended for the addressee. Should you receive this message by mistake, you are hereby notified that any disclosure, reproduction, distribution or use of this message is strictly prohibited. Please inform the sender by reply transmission and delete the message without copying or opening it. Messages and attachments are scanned for all viruses known. If this message contains password-protected attachments, the files have NOT been scanned for viruses by the ING mail domain. Always scan attachments before opening them. -----------------------------------------------------------------
