![]() This document goes a little further than most in some areas however it is likely that these extensions will not conflict with most other coding standards. For this reason many coding standards are broadly compatible with each other. Most coding standards derive at least some of their content from the Hungarian notation concept and in particular from a Microsoft white paper that documented a set of suggested naming standards. It is not uncommon for programmers to work with customers that have their own coding standards. You might choose to adopt this standard for major additions to existing systems or when you are adding code that you think will become part of a code library that already uses this standard.Ĭode written for customers that require that their standards be adopted. In general, it is a good idea to make your changes conform to the surrounding code style wherever possible. This document applies to ALL CODE except the following :Ĭode changes made to existing systems not written to this standard. However, there are some cases where it is impractical or impossible to apply these conventions, and others where it would be A Bad Thing. It is the intention that all code adhere to this standard. However, do not assume that this document is any less important or should be treated any less lightly than its drier cousins. Some standards documents are so dry as to be about as interesting as reading the white pages. Hopefully this document is actually readable. We have tried to actually think about the relative merits of each alternative but inevitably some personal preferences have come into play. Inevitably, there are many places in this document where we have simply had to make a choice between two or more equally valid alternatives. This document is a working document - it is not designed to meet the requirement that we have "a" coding standard but instead is an acknowledgement that we can make our lives much easier in the long term if we all agree to a common set of conventions when writing code. 19 Cradle to Grave Naming of Data Items.17 Specifying Particular Control Variants - NOT. ![]() 3.2 Name body casing does not apply to prefixes and suffixes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |