Com S 641 meeting -*- Outline -*- * summary (3.9) ------------------------------------------ SUMMARY (3.9) "A parameterized abstraction is just Hence, lambda abstractions, \I:t . U Language satisfies parameterization principle if: ------------------------------------------ ... an abstraction whose body is a parameterized phrase" This separates the roles of parameterization and abstraction ... t can be any type ------------------------------------------ DESIGN METHOD Start with core: - add abstraction forms - add parameter forms Correspondence: makes sure treatment of identifiers that name abstractions and parameters is the same At each step give: - syntax - type attributes - typing rules - denotational semantics - soundness proof ------------------------------------------ Q: Are abstraction and parameterization independent (orthogonal) extensions to the core? It doesn't seem so (despite Schmidt's claim), since they both use identifiers. The whole point of the correspondence principle is to avoid bad interactions!