G.T.: Quantified, typed events for improved separation of concerns

Implicit invocation and aspect-oriented languages provide related but distinct mechanisms for separation of concerns. Implicit in-vocation languages have explicitly announced events, which runs registered observer methods. Aspect-oriented languages have im-plicitly announced events, called “join points, ” which run method-like but more powerful advice. A limitation of implicit invocation languages is their inability to refer to a large set of events suc-cinctly. They also lack the expressive power of aspect-oriented ad-vice, and require code to manage event registration and announce-ment. Aspect-oriented languages also have several limitations, in-cluding the potential for fragile dependence on syntactic structure that may hurt maintainability, limits in the set of join points and the reflective contextual information that they make available. Quantified, typed events solve all these problems. They ex-tend implicit invocation languages with a key idea from aspect-oriented languages: the ability to quantify over events (join points). Programmers declare named event types that contain information about the names and types of event arguments (exposed context). An event type declaratively identifies an expression as an event. This event type can then be used to quantify over all such events. Event types reduce the coupling between the observers and the set of events, and similarly between the advising and advised code. 1