RE: CL programming standards

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

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Experience is the name everyone gives to their mistakes."
-- Oscar Wilde

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

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
comments)



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 http://www.symanteccloud.com
______________________________________________________________________
--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.