Parallel Tools Consortium
Naming Conventions for Ptools Projects
This page documents the naming conventions established by and
for Ptools projects. As individual working groups expand on these
conventions, they are asked to send additions to the contact listed
at the bottom.
Names associated with standard APIs
Each Ptools project should establish a "project prefix" that will
be used to distinguish user-referenced names from other system or
user-defined names. Typically, such a prefix will be 2-4 characters
in length (e.g., "LCB," "PTR," or "DAQV").
- library routines that will be invoked by users should
begin with the project prefix, in caps, followed by an
underscore and the name of the routine. Examples:
- header files to be #included by users will be
of the form ptools_project-prefix.h.
Where it is necessary to distinguish multiple header files,
these names can be extended in ways similar to other standard
software distributions. Examples:
ptools_ptr_f.h (language specific)
ptools_daqv_sgi.h (platform specific)
- library files to be linked to user applications will be
of the form
libptools_ptr_f.a (language specific)
libptools_daqv.so.0.55 (sharable library)
Last updated March 8, 1996.
Additions and queries to Sam Coleman,