The default file name is determined by the name of the unit that the file contains. The name is formed by taking the full expanded name of the unit and replacing the separating dots with hyphens and using lowercase for all letters.
An exception arises if the file name generated by the above rules starts
with one of the characters
s, and the second character is a
minus. In this case, the character tilde is used in place
of the minus. The reason for this special rule is to avoid clashes with
the standard names for child units of the packages System, Ada,
Interfaces, and GNAT, which use the prefixes
The file extension is
.ads for a spec and
.adb for a body. The following table shows some
examples of these rules.
Source File Ada Compilation Unit
Arith_Functions (package spec)
Arith_Functions (package body)
Func.Spec (child package spec)
Func.Spec (child package body)
Sub (subunit of Main)
A.Bad (child package body)
Following these rules can result in excessively long file names if corresponding unit names are long (for example, if child units or subunits are heavily nested). An option is available to shorten such long file names (called file name ‘krunching’). This may be particularly useful when programs being developed with GNAT are to be used on operating systems with limited file name lengths. Using gnatkr.
Of course, no file shortening algorithm can guarantee uniqueness over all possible unit names; if file name krunching is used, it is your responsibility to ensure no name clashes occur. Alternatively you can specify the exact file names that you want used, as described in the next section. Finally, if your Ada programs are migrating from a compiler with a different naming convention, you can use the gnatchop utility to produce source files that follow the GNAT naming conventions. (For details see Renaming Files with gnatchop.)
Note: in the case of Windows or Mac OS operating systems, case is not
significant. So for example on Windows if the canonical name is
main-sub.adb, you can use the file name
However, case is significant for other operating systems, so for example,
if you want to use other than canonically cased file names on a Unix system,
you need to follow the procedures described in the next section.