Implicit invocation of traits

Authors:
Thomas Pawlitzki;Friedrich Steimann
Affiliations:
Fakultät für Mathematik und Informatik, Fernuniversität in Hagen, Hagen, Germany;Fakultät für Mathematik und Informatik, Fernuniversität in Hagen, Hagen, Germany
Venue:
Proceedings of the 2010 ACM Symposium on Applied Computing
Year:
2010

Citing 10
Cited 0

Reconciling environment integration and component independence

SDE 4 Proceedings of the fourth ACM SIGSOFT symposium on Software development environments
Design patterns: elements of reusable object-oriented software

Design patterns: elements of reusable object-oriented software
Reasoning about implicit invocation

SIGSOFT '98/FSE-6 Proceedings of the 6th ACM SIGSOFT international symposium on Foundations of software engineering
Connecting Tools Using Message Passing in the Field Environment

IEEE Software
Formalizing Design Spaces: Implicit Invocation Mechanisms

VDM '91 Proceedings of the 4th International Symposium of VDM Europe on Formal Software Development-Volume I: Conference Contributions - Volume I
Understanding Aspects via Implicit Invocation

Proceedings of the 19th IEEE international conference on Automated software engineering
Classpects: unifying aspect- and object-oriented language design

Proceedings of the 27th international conference on Software engineering
The paradoxical success of aspect-oriented programming

Proceedings of the 21st annual ACM SIGPLAN conference on Object-oriented programming systems, languages, and applications
Type-based publish/subscribe: Concepts and experiences

ACM Transactions on Programming Languages and Systems (TOPLAS)
Types and modularity for implicit invocation with implicit announcement

ACM Transactions on Software Engineering and Methodology (TOSEM)

Quantified Score

Hi-index	0.00

Visualization

Abstract

We propose the introduction of a special kind of traits that implement methods implicitly invoked when an event of a given type occurs. Events are announced explicitly in the source code at their place of origin, and classes publishing events, as well as traits subscribing to them, are explicitly marked as such. The result is greater independence of publisher and subscriber (when compared to other implementations), as well as an explicit interface between the two. An implementation in Scala is briefly sketched.