Anonymous user
Compile time: Difference between revisions
m
Moved to life cycle cat, link
m (added some links, spelling/grammar) |
m (Moved to life cycle cat, link) |
||
Line 1:
[[Category:Program life cycle]]'''Compile time''' refers to the compilation phase of the program life cycle. The actions undertaken at this stage are referred as ''compile-time'', ''static'', and sometimes as ''early''. The term ''static'' is used in order to stress that the properties provable at compile-time stay valid for the program as a whole, and thus do not depend on the program's dynamic execution state. The term ''early'' is used as an opposite to ''late''.▼
In particular [[type checking|statically typed]] languages are often backed with the argument that errors need to be detected as early as possible. Some languages were specifically designed in a way to support an extensive static analysis of the program semantics.▼
▲'''Compile time''' refers to the compilation phase of the program life cycle. The actions undertaken at this stage are referred as ''compile-time'', ''static'', and sometimes as ''early''. The term ''static'' is used in order to stress that the properties provable at compile-time stay valid for the program as a whole, and thus do not depend on the program's dynamic execution state. The term ''early'' is used as an opposite to ''late''.
▲In particular statically typed languages are often backed with the argument that errors need to be detected as early as possible. Some languages were specifically designed in a way to support an extensive static analysis of the program semantics.
The phases following to compile time are [[link time]] and [[run time]].
| |||