![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
More on Compilation StatesUsing compilation commands, you can parse, analyze, compile, and link program units in the compilation context of the view associated with the units. The compiler that is used, the values of compiler switches, and the imported views that provide external visibility are all established by the view context.
Each compilation command produces permanent information that is used by succeeding commands. For example, In Ada, the Compile > Analyze command provides semantic information about the meaning of the units that is later used to generate code.
The compilation states are described below:
- Archived
The unit has no compiler-related information. Either the unit has never been processed by the compiler or all compiler information has been removed.
- Source
The unit has been parsed. The Import_Text_File or Compile > Parse (Ada only) command advances the unit to this state.
- Installed
The unit has been checked for semantic consistency. The Compile > Analyze (Ada) command advances the unit to this state.
- Coded
Object code has been generated for the unit. The Compile > Code command advances the unit to this state.
- Linked
An executable has been generated based on this unit. The Linked state only applies to the body of the subprogram. The Compile > Link command advances the unit to this state.
- Unparsed
The unit's source file has been updated since the compiler was last run.
If you skip a compilation step, the lower compilation commands are superseded by the higher one. For example, if you execute Compile > Code on a unit without executing Compile > Analyze, the Code command does an implicit Analyze.
More information on Ada compilation can be found in the Ada Compiler Reference.
Rational Software Corporation http://www.rational.com support@rational.com techpubs@rational.com Copyright © 1993-2001, Rational Software Corporation. All rights reserved. |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |