4.3.3 Multiple File Tests

When tests are contained in multiple files (i.e., compilation units are contained in different files), the file names are related. The first seven positions of the names of all the files (other than foundation files) comprised by a single test will be identical. The eighth position will provide a distinguishing alphanumeric which indicates the required compilation order. In legacy tests, the main subprogram is not indicated (see the table in section 4.3.1 for files containing main subprograms). For newer (modern) tests, the extension ".am" indicates the file with the main subprogram.

All tests apply the convention of naming the main subprogram the same as the file (excluding the file extension) plus, for legacy tests only, the letter 'm'. For example, the legacy test, C39006F, is contained in four files, named c39006f0.ada, c39006f1.ada, c39006f2.ada, and c39006f3.ada. The main subprogram of the test is contained in c39006f3.ada and is named C390006F3M. The test C390006 is also contained in four files, named c3900060.a, c3900061.a, c3900062.a, and c3900063.am. The main subprogram of the test is contained in c3900063.am and is named C3900063.

Unless otherwise required by a test objective, other library units in a test are named with the test name and a suffix. Typically, the suffix will be a number or an underscore followed by a few letters. Similarly, library units making up a foundation are usually named with the foundation name (or the foundation name and a suffix if there are multiple units in the foundation). This convention reduces name collisions with other tests and with implementation-defined units.

There are a small number of Specialized Needs Annex tests for the Distributed Processing Annex that require two active partitions and have two main subprograms. These tests have two files with the .am extension to signify the location of the (multiple) main subprograms.