|
I agree with Scott that not that much changes. Everything below except for the spacing, could be applied to fixed as well as /free. That being said, I based our style on our Java style, which I got here: http://www.javaranch.com/style.jsp Obviously not everything translates, but mixed case naming and semi-colon placement are the same. My documentation even resembles JavaDoc. Here are some other standards/guidelines we employ: - Indent 2 spaces per level starting under the 'r' in /free. - If you have to wrap a line of code more than once you are either nested too far or the line is too complicated. - All database files are prefixed. - File field names are in ALLCAPS. - Qualified datastructures are recommended but not required. - Only use named indicators. - No compile time tables/arrays, inz DS subfields instead. Naturally this all applies to new code... Joel http://www.rpgnext.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.