As described in chapter 4, page 279, unit description les (hereafter called PPU les for short), are
used to determine if the unit code must be recompiled or not. In other words, the PPU les act as
mini-make les, which is used to check dependencies of the di erent code modules, as well as verify
if the modules are up to date or not. Furthermore, it contains all public symbols de ned for a
module.
The general format of the ppu le format is shown in gure (A.1).
To read or write the ppu le, the ppu unit ppu.pas can be used, which has an object called tppu le
which holds all routines that deal with ppu le handling. While describing the layout of a ppu le,
the methods which can be used for it are presented as well.
A unit le consists of basically ve or six parts:
- A unit header.
- A general information part (wrongly named interface section in the code)
- A de nition part. Contains all type and procedure de nitions.
- A symbol part. Contains all symbol names and references to their de nitions.
- A browser part. Contains all references from this unit to other units and inside this
unit. Only available when the uf_has_browser ag is set in the unit ags
- A le implementation part (currently unused).
