A quantitative analysis of aspects in the eCos kernel

Lohmann, Daniel; Scheler, Fabian; Tartler, Reinhard; Spinczyk, Olaf; Schröder-Preikschat, Wolfgang

doi:10.1145/1217935.1217954

Cited by 67 publications

(69 citation statements)

References 31 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…While many studies have explored the capabilities of aspect-oriented programming (AOP) [1] to improve the modularity, customization, and evolution of software [2,3,4,5,6,7,8], little is known on how AOP has been used. As AspectJ 1 is the most widely used AOP language, we want to know which AspectJ mechanisms are used, to what extent, and for what kinds of crosscutting concerns.…”

Section: Introductionmentioning

confidence: 99%

How AspectJ is Used: An Analysis of Eleven AspectJ Programs.

Apel¹

2010

JOT

View full text Add to dashboard Cite

Abstract. While it is well-known that crosscutting concerns occur in many software projects, little is known on how aspect-oriented programming and in particular AspectJ have been used. In this paper, we analyze eleven AspectJ programs by different authors to answer the questions: which mechanisms are used, to what extent, and for what purpose. We found the code of these programs to be on average 86 % objectoriented, 12 % basic AspectJ mechanisms (introductions and method extensions), and 2 % advanced AspectJ mechanisms (homogeneous advice or advanced dynamic advice). There is one class of crosscutting concerns -which is mostly concerned with introductions and method extensions -that matches this result well: collaborations. These results and our discussions with program authors indicate the bulk of coding activities was implementing collaborations. Several studies and researchers suggest that languages explicitly supporting collaborations are better suited than aspectsà la AspectJ for this task.

show abstract

Section: Introductionmentioning

confidence: 99%

How AspectJ is Used: An Analysis of Eleven AspectJ Programs.

Apel¹

2010

JOT

View full text Add to dashboard Cite

show abstract

“…It consists of an aspect weaver that processes ordinary C++ code and aspect code, and weaves the latter type of code into the C++ files at the relevant locations (i.e., join points). Thus, the advice code is inlined into existing C++ code and produces no overhead compared to an implementation by hand (see [23]). In constrast to C preprocessor directives, the AspectC++ language elements are fully integrated into the syntax and semantics of C++.…”

Section: Aspect-oriented Programmingmentioning

confidence: 99%

Technische Universität Dortmund

2017

Geschichte Der Anorganischen Chemie

View full text Add to dashboard Cite

Internet protocols are constantly gaining relevance for the domain of mobile and embedded systems. However, building complex network protocol stacks for small resource-constrained devices is more than just porting a reference implementation. Due to the cost pressure in this area especially the memory footprint has to be minimized. Therefore, embedded TCP/IP implementations tend to be statically configurable with respect to the concrete application scenario. This paper describes our software engineering approach for building CiAO/IP -a tailorable TCP/IP stack for small embedded systems, which pushes the limits of static configurability while retaining source code maintainability. Our evaluation results show that CiAO/IP thereby outperforms both lwIP and uIP in terms of code size (up to 90% less than uIP), throughput (up to 20% higher than lwIP), energy consumption (at least 40% lower than uIP) and, most importantly, tailorability.

show abstract

“…In fact, for static pointcuts Yiihaw seems to incur even less overhead than AspectC++ because some shortcomings in current C++ compilers slightly impair the performance of AspectC++ [26].…”

Section: Related Work: Other Aspect Weaversmentioning

confidence: 99%

Zero-Overhead Composable Aspects for .NET

Johansen

Sestoft

Spangenberg

2008

Advances in Software Engineering

View full text Add to dashboard Cite

Abstract. We present a new static aspect weaver for C#. The weaver, which is called Yiihaw, works by transforming a program's bytecode and types, stored in so-called assemblies, and performs extensive checks at weave-time to ensure correctness of the resulting woven assembly. The design makes four contributions: (a) Application of generic advice is typesafe; (b) application of "around" advice incurs no runtime overhead; (c) woven assemblies can be further woven; and (d) advice can itself be woven before being applied to target code -in effect advice can be composed. These contributions are achieved by minimal means, basing much of the type checking on the bytecode's generic type system. Yiihaw's aspects are less expressive than those of AspectJ: an aspect does not have an identity of its own; only static join points are supported; and the pointcut language does not allow logical combinations of join points. However, Yiihaw is sufficiently expressive for many purposes, and for these purposes it provides statically typesafe weaving and highly efficient woven code.

show abstract

A quantitative analysis of aspects in the eCos kernel

Cited by 67 publications

References 31 publications

How AspectJ is Used: An Analysis of Eleven AspectJ Programs.

How AspectJ is Used: An Analysis of Eleven AspectJ Programs.

Technische Universität Dortmund

Zero-Overhead Composable Aspects for .NET

Contact Info

Product

Resources

About