Never have the word "never" associated with any requirement. Think and
write positively, and explain where exceptions shall be required.

Dennis Lovelady
"Experience is the name everyone gives to their mistakes."
-- Oscar Wilde

What are some of the CL programming standards that your shop has found

I would think that a few standards are NEVER have the following in
production CL:

- never have a library name in CL (OK allow QTEMP)

- never have even a variable library name in CL

- never have a person's name or email address in CL (OK in author

Would a library in CL ever be necessary? I would think that good
coding would allow the *libl to do the work of choosing the correct lib
in almost all cases.

Comments and additional good practices?

This outbound email has been scanned for all viruses by the MessageLabs
Skyscan service.
For more information please visit
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by 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].