Names for Files

Version 1.9 Build 803

News	FAQ
Search	Home

Next: Format for Dates Up: Documentation and Naming Previous: Names for Classes, Functions and Variables

Names for Files

The only restrictions here are commonsense, and the Unix library archive utility ``ar''. It is strongly suggested that the file name equals the name of the one or dominant class in the file. The above suggests that file names should be long enough to convey meaning to the reader, but not so long as to be a burden to type. This translates to: file names should be from about 8 to about 30 characters long.

``ar'' requires that all object file names be unique in the first 14 characters.

Underscores are not allowed in file names.

Any file (a shell script, or a C++ program, for example) which can be invoked at the command line as an executable program, must be named with lower case chararacters only. (This policy follows the glish function naming policy of the previous section; both are designed to present the end user with only lower case commands to type, but note that underscores are prohibited in file names.)

Use the standard extensions (.c, .cc, .h, .f, .g).

Next: Format for Dates Up: Documentation and Naming Previous: Names for Classes, Functions and Variables Contents Index