|
Many developers from different organizations derive new classes from existing
ACIS classes. To reduce the potential for name collisions and to identify owning organizations of derived classes, the first derivation from an
ACIS class is always an "organization class." The organization class merely identifies the organization using a two or three-character
sentinel, which is a unique identifier that prevents name collisions and identifies the "owner" of the class. The organization sentinel may identify a company or component. Refer to section
Sentinels in this chapter.
|
|
|
Organization classes define no methods or data of their own.
Organization classes are never instantiated. Application-specific classes are derived from the organization class. They define data and methods and can be instantiated.
|
|
|
The assembly modeling example illustrates the organization class,
ENTITY_XYZ, and two application-specific classes,
ASSEMBLY and
INSTANCE.
|