DynBindModel: Difference between revisions
| Line 32: | Line 32: | ||
<math>\tau : \mathrm{TYPE} \rightarrow \left( \mathrm{NAME} \rightarrow \mathrm{FEATURE} \right)</math> | <math>\tau : \mathrm{TYPE} \rightarrow \left( \mathrm{NAME} \rightarrow \mathrm{FEATURE} \right)</math> | ||
Gives information about the features declared in a class. | |||
Revision as of 21:53, 1 October 2006
Motivation:
Eiffels dynamic binding is somewhat more complex than that of other languages. Its structure is still very simple and can be described by giving the relation γ:
Relation γ contains both the static and dynamic binding part of the language. In the following feature:
f (a: ANY)
do
print (a.out)
end
The static binding part of call a.out can be decribed as:
Namely an evaluation of γ with a tuple containing the static type of the call and the name. The result of this is a function. This function will be evaluated at runtime and yield the right feature according to the dynamic type of a.
In the rest of this text, the we will show how to construct the relation γ based on any given eiffel system.
Some fundamentals
We introduce the operator as the "ancestor of" and as "descendant of" operator.
Without loss of generality we can say that any Eiffel system consists of a set of classes such that if . In practice class will allways be class ANY but this is not of importance here.
The relation
Gives information about the features declared in a class.