Binary component adaptation

Keller, R.; Hölzle, Urs

doi:10.1007/bfb0054097

Cited by 97 publications

(90 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Others have proposed dynamic load-time class overriding through byte-code editing [6]. This technique is justified by the so-called adaptation and evolution problems that appear when sub-classing is used to build software components.…”

Section: Discussionmentioning

confidence: 99%

Derivation of Secure Parallel Applications by Means of Module Embedding

Radenski

2000

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

Section: Discussionmentioning

confidence: 99%

Derivation of Secure Parallel Applications by Means of Module Embedding

Radenski

2000

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…We have experimented with OpenJava to an extent that we are confident regarding its suitability for an implementation of MCI that covers full Java. Instead of instrumenting source code, one can also consider byte-code engineering as supported by JMangler, BCA, or Javassist [6,27,14]. Byte-code transformation can either happen at class-load time, or offline.…”

Section: Related Workmentioning

confidence: 99%

Semantics-directed implementation of method-call interception

Lämmel

Stenzel

2004

IEE Proc., Softw.

View full text Add to dashboard Cite

C e n t r u m v o o r W i s k u n d e e n I n f o r m a t i c aSemantics-Directed Implementation of Method-Call Interception ABSTRACT We describe a form of method-call interception (MCI) that allows the programmer to superimpose extra functionality onto method calls at run-time. We provide a reference semantics and a reference implementation for corresponding language constructs. The setup applies to class-based, statically typed, compiled languages such as Java. The semantics of MCI is used to direct a language implementation with a number of valuable properties: simplicity of the implementational model and run-time adaptation capabilities and static type safety and separate compilation and reasonable performance. Our implementational development employs sourcecode instrumentation. We start from a naive implementational model, which is subsequently refined to optimise program execution. The implementation is assessed via benchmarks. ACM Computing Classification AbstractWe describe a form of method-call interception (MCI) that allows the programmer to superimpose extra functionality onto method calls at run-time. We provide a reference semantics and a reference implementation for corresponding language constructs. The setup applies to class-based, statically typed, compiled languages such as Java. The semantics of MCI is used to direct a language implementation with a number of valuable properties: simplicity of the implementational model and run-time adaptation capabilities and static type safety and separate compilation and reasonable performance. Our implementational development employs sourcecode instrumentation. We start from a naive implementational model, which is subsequently refined to optimise program execution. The implementation is assessed via benchmarks.

show abstract

“…BCA [15] is a system using byte-code translation to enhance the reusability of existing class libraries. The programmers can modify the existing classes without source-code by describing the difference, called delta files.…”

Section: Applicationmentioning

confidence: 99%

Difference-Based Modules: A Class-Independent Module Mechanism

Ichisugi

Tanaka

2002

ECOOP 2002 — Object-Oriented Programming

View full text Add to dashboard Cite

Abstract. We describe a module mechanism, which we call differencebased modules, and an object-oriented language we call MixJuice. MixJuice is an enhancement to the Java language that adopts difference-based modules instead of Java's original module mechanism. Modules are units of information hiding, reuse and separate compilation. We have completely separated the class mechanism and the module mechanism, and then unified the module mechanism and the differential programming mechanism. Although this module mechanism is simpler than that of Java, it enhances ease with which programs can be extended, reused and maintained. Collaborations that crosscut several classes can be separated into different modules. Modules are composable in the same way as mixins. The composition of modules sometimes causes name collision and an interesting phenomenon, which we call implementation defects. We describe solutions to these problems.

show abstract

Binary component adaptation

Cited by 97 publications

References 18 publications

Derivation of Secure Parallel Applications by Means of Module Embedding

Derivation of Secure Parallel Applications by Means of Module Embedding

Semantics-directed implementation of method-call interception

Difference-Based Modules: A Class-Independent Module Mechanism

Contact Info

Product

Resources

About