![]() |
![]() |
|
![]() |
Paradox For Windows Naming Conventions © 2001 J. Eric Taylor Introduction The naming conventions listed here are an adaptation of the conventions suggested by the books Paradox For Windows Applications by Bill Todd and Code Complete by Steve McConell. A suffix based naming convention works well for our firm. If your experience has been primarily with Hungarian notation, you may prefer to adapt these conventions to a prefix based system ( instead of suffix ) of your own. "The most important consideration in naming a programming item is that the name fully and accurately describe the entity and/or the variable represents. Entity names should be readable, memorable and appropriate." (paraphrased) Variables and Constants Intercaps with first letter capitalized will be used with variables and constants. Special characters and numbers are discouraged. Variable and Constant names of more than 16 characters will not be uncommon using these guidelines. Variables and constants will end with a suffix to reflect their position in the container hierarchy.
All global variables and constants will be labeled "Global". They will have the suffix of " _GV " or " _GC " Private variables and constants will have no special suffixes. Always use Persistent Variables and Constants scoped to the object before considering global variables. Avoid global variables where ever possible! Persistent variables are declared above the method. Once assigned the persist for the life of the object. Use constants as much as possible to make code changes easier and faster to manage. Initialize variables in the built-in Init or Open methods whereever possible.
Variable Naming Conventions
Uiobject Naming Conventions
Fields Naming fields in a table correctly improves software ease of use and reuse just as much, if not more, than naming conventions applied to variables and Uiobjects. All fields will begin with a three letter prefix, all in capitol letters, indicating the table to which they belong. It is acceptable to end the field name with a three letter suffix, based on the variable naming conventions listed above, to indicate the data type of the field. Intercaps will be used throught the various names. Field names of more than 16 characters will not be uncommon using these guidelines. Formula: Table Name + Field Name + Data Type Field Naming Conventions
Custom Methods Custom methods will be named with a strong action verb followed by the object of the action verb and finally with the datatype the custom method returns. If a custom method does not return a data type then the suffix will be Nil. Formula: Action Verb + Object of Action + Returned Data Type
Position Variables
Discussion of this article |
![]() Feedback | Paradox Day | Who Uses Paradox | I Use Paradox | Downloads ![]() |
|
![]() The information provided on this Web site is not in any way sponsored or endorsed by Corel Corporation. Paradox is a registered trademark of Corel Corporation. ![]() |
|
![]() Modified: 15 May 2003 Terms of Use / Legal Disclaimer ![]() |
![]() Copyright © 2001- 2003 Paradox Community. All rights reserved. Company and product names are trademarks or registered trademarks of their respective companies. Authors hold the copyrights to their own works. Please contact the author of any article for details. ![]() |
![]() |
|