Naming conventions



next up previous
Next: The Unifpack libraries Up: A reference Guide Previous: Some words about

Naming conventions

Unifpack uses the following conventions, there are some exceptions that should be solved in the near future, it is also important to notice that Unifpack has no standard prefix yet.

All filenames in Unifpack should be lowercase, with a name of at most 8 chars and and extension of at most 3 chars, this is for easing ports to MS-DOS and other environments. gif Some files that have a uppercases such as Makefile, this usually is OK as long as no conflict is produced if the OS is case insensitive. The non-standard extension .ph stands for Private Header, this header file should be included only by the code of a class and ``friend'' functions, including them in other context could violate the data-hiding mechanism.

Functions and type names all should start with an uppercase letter, different words in the name are signaled by capitalizing the first letter of each word, preprocessor symbols are all capital letters, different words separated by underscores. Global variables follow the same convention but they start with a lowercase letter, or, if it is intended that the user will not use it, by two underscores.

The class name and data-hiding follow the methods described in the above example. The function name of a class method starts with the name of the class, like WordSize(Word)



coryan@mat.puc.cl