Results 1 -
3 of
3
Pluggable Verification Modules: An Extensible Protection Mechanism for the JVM
- IN PROCEEDINGS OF THE 19TH ANNUAL ACM SIGPLAN CONFERENCE ON OBJECT-ORIENTED PROGRAMMING, SYSTEMS, LANGUAGES, AND APPLICATIONS (OOPSLA’04
, 2003
"... ..."
A Virtual Machine for Multi-Language Execution
- Programming Systems Lab, Universität des Saarlandes, Saarbrücken
, 2002
"... This paper presents the architecture of a virtual machine designed specifically for the execution of multiple languages, which we call Seam. The architecture consists of a number of generic components, usable by all languages, and of a number of interfaces for which implementations have to be provid ..."
Abstract
-
Cited by 8 (5 self)
- Add to MetaCart
This paper presents the architecture of a virtual machine designed specifically for the execution of multiple languages, which we call Seam. The architecture consists of a number of generic components, usable by all languages, and of a number of interfaces for which implementations have to be provided by language implementors. Our contribution is the identification of the generic services and the clean design for the parameterization over their language-specific aspects. The goal of Seam is to provide both for ample reuse and simple language implementation, concerning both compilers and runtime components, and to be a platform for language interoperation. We have implemented a prototype version of Seam and validated it with two language implementations. We present a full running implementation of Alice and a nave implementation of a Java Virtual Machine running on Seam. The paper presents first implementation e#ort and performance results for the prototype.
Application-Level Concurrency Management
, 2003
"... Traditionally an execution environment faces a trade-off between providing high-level or low-level concurrency mechanisms. The former trades flexibility for ease-of-use, while the latter results in a concurrency management closer to applications needs at the cost of an increase in the complexity ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
Traditionally an execution environment faces a trade-off between providing high-level or low-level concurrency mechanisms. The former trades flexibility for ease-of-use, while the latter results in a concurrency management closer to applications needs at the cost of an increase in the complexity of the applications code. Thus, one way or another, an application programmer has to match his application's semantic to the set of abstractions exported by the target execution environment.

