PhysicalName Class

The PhysicalName class is used to help manage repeated capability physical names. Repeated capability physical names can be nested or non-nested and can be qualified or non-qualified. The PhysicalName class exposes functions for accessing these features of repeated capability physical names.

The PhysicalName class is a template class which is bound to the type of a specific repeated capability class declared within the driver. Instances of the PhysicalName class can also be associated with a parent repeated capability in order to manage nested repeated capability physical names. These associations provides for compile-time type safety when using the PhysicalName class.

For example, the AncestorName, AncestorFullName, and AncestorIndex functions do not exist when creating a PhysicalName instance for a non-nested repeated capability, because non-nested repeated capabilities obviously have no ancestors. Attempting to invoke any of those functions on a non-nested PhysicalName instance will yield a compile-time error, which is far preferrable to a runtime error that may reach the end user and which they would have no understanding of how to address.

The topics in this section present each of the member functions PhysicalName class along with examples of their usage.