It is our great pleasure to host the fourth edition of the Domain-Specific Aspect Languages workshop (DSAL09), as part of the eight International Conference on Aspect-Oriented Software Development (AOSD09).
The tendency to raise the abstraction level in programming languages towards a particular domain is also a major driving force in the research domain of aspect-oriented programming languages. The DSAL workshop series aims to bring the research communities of domain-specific language engineering and domain-specific aspect design together. In the editions held at GPCE06/OOPSLA06 and AOSD07 we approached domain-specific aspect languages both from a design and a language implementation point of view. At AOSD08 we explicitly invited contributions of work on adding domain-specific extensions (DSXs) to general-purpose aspect languages (GPALs). We continue this trend for this edition as the focus on language embedding raises specific issues for language designers, such as proper symbiosis between, and composition of, DSXs.
The workshop Call For Papers sought contributions related to domain-specific aspect languages, more particularly (but not limited to):
design of DSALs and DSXs
successful DSALs, DSXs and their applications
issues in both design and implementation of DSALs and DSXs
methodologies and tools suitable for creating DSALs and DSXs
semantics and composition of DSALs and DSXs
disciplined approaches for invasive metaprogramming
error reporting in DSALs and debugging of DSALs
approaches for composable language embeddings
mechanisms for interaction detection and handling in DSALs
theoretical foundations for DSALs
analysis about the specificity spectrum in aspect languages
key challenges for future work in the area
This year we accepted 5 papers for presentation and publication, 3 short papers and 2 technical papers. We would like to thank all paper submitters for contributing to the work on domain-specific aspect languages, the authors of accepted papers for providing the discussion material for this year, and last but not least the program committee for their swift reviews.
Proceeding Downloads
Untangling crosscutting concerns in domain-specific languages with domain-specific join points
Like programs written in general-purpose languages, programs written in DSLs may also suffer from tangling and scattering in the presence of domain-specific crosscutting concerns. This paper presents an architecture that supports aspect-oriented ...
AOP for the domain of runtime monitoring: breaking out of the code-based model
Runtime monitoring, even the canonical "logging" example of AOP, has long been one of the domains into which AOP has effectively been deployed. Yet to date AOP has not supported the full breadth of needs across the scope of widely varied runtime ...
Sectional domain specific languages
Nowadays, many problems are solved by using a domain specific language (DSL), i.e., a programming language tailored to work on a particular application domain. Normally, a new DSL is designed and implemented from scratch requiring a long time-to-market ...
Aspect-oriented generation of the API documentation for AspectJ
Through the development of a framework or a class library, writing the document on their application programming interface (API) is essential. The document on the API, which we call the API documentation, is mainly read by programmers who want to ...
A proposal for extensible AspectJ
- Vladimir Oliveira Di Iorio,
- Leonardo Vieira dos Santos Reis,
- Roberto da Silva Bigonha,
- Mariza Andrade da Silva Bigonha
This article presents the preliminary results achieved while working with a language to define extensions to the concrete syntax of AspectJ. The language uses the concept of syntax classes, units that extend classes with syntax definitions, building ...
Cited By
Recommendations
First-class domain specific aspect languages
MODULARITY Companion 2015: Companion Proceedings of the 14th International Conference on ModularityProgramming in a domain specific aspect language (DSAL) typically involves some language workbench for transforming the DSAL code and some AOP composition framework for weaving the transformed code. However, DSAL development remains second-class in two ...