Naming Conventions


When you extend ACIS with the addition of your own C++ code, follow these naming conventions to avoid issues.

Sentinels

To avoid naming collisions between developers who create new C++ code that is linked with ACIS, Spatial requires the use of a sentinel. A sentinel is a two or three character string which is embedded in class and API function names, and identifies the development organization. Every new API and class derived from ENTITY or ATTRIB uses this sentinel as part of its name (this is described in specific documentation about creating new APIs and deriving classes). The sentinel ensures that developers do not apply the same name to a function or class.

Note:  Contact Spatial Customer Support to have a unique sentinel assigned to your ACIS development project.

Filenames

To avoid naming collisions, the filenames you use when extending ACIS must be unique (they cannot conflict with the names of files existing in ACIS).

[Top]