|
|
|
The compiler accepts any IMPORT sequence, but the definitions are not imported during compilation. The list of imports are remembered in the compiled output, and the requested definitions imported only during map load in their compiled version. Hence compilation is performed without resolving that all type definitions exist for the module. However, the load fails unless resolution is complete following the import phase.
When a typeReference is imported, all contained component definitions are imported, plus all supporting typeReferences. Thus importing represents a convenient technique for rationalizing definitions such that several specific maps can include a set of common definitions. Import resolution is discussed further in the section dealing with map loading. In the map being used for importing, the export sequence must contain the name of the Type Reference that is being imported.
| Copyright © 2008 CA. All rights reserved. |
|