| |
| |
Static typing and other mysteries of life |
 | | The policy known as static typing, which I will argue is the only reasonable one for professional software development, states that we should answer the "when" part of the question by "before we ever think of running the system", and the "how" part by "through mere examination of the software text". |
 | | Static binding, which if I understand properly is the default C++ policy, would mean that we disregard the object type and believe the entity declaration, leading us for example to apply to a Boeing 747-400 the version of a feature, such as lower_landing_gear, that has been defined for the standard Boeing 747 planes. |
 | | Static typing, as in Eiffel, means performing the check before any execution of the software; typically, this will be part of the verifications made by a compiler. |
| archive.eiffel.com /doc/manuals/technology/typing/paper/page.html (4425 words) |
|