Getting Started

Documentation

Glish

Learn More

Programming

Contact Us

Version 1.9 Build 803

News	FAQ
Search	Home

Modules

Closely related classes should be organized into a module - which requires an appropriately named, separate directory.^6.9 Modules are assigned by the AIPS++ system manager. The module will have a ``module header file'' - whose primary purpose is to simplify things for the application programmer by providing sufficient help information for the general use of the classes in the module. Whenever possible, application programmers should not be required to learn the intricacies of a complicated module, nor to understand specific implementation classes within the module. In these cases they should only have to include a single header file into their application program. In cases where the role of the module is more a conglomerate of related, but independent, classes, individual header files should be used.^6.10

The module header file ^6.11 will live in the module's parent directory: code/aips/implement/Tables.h, for example, is the module header file for, and describes the classes in code/aips/implement/Tables/.