|
|||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||
ABSTRACT
Among the key reasons why the Java platform has become the most popular programming language for traditional non-real-time development are its portability across a wide variety of popular operating systems and architectures and its built-in language support for threading and synchronization [1, 2]. These are both critical enablers for the creation of a vibrant after market for commercial off the shelf and open source software components. And they are key reasons why software maintenance and reuse of Java software is typically five to ten times less expensive than comparable activities for software implemented in C or C++ [3, 4]. The portable thread model defined by the Java Language Specification [5] does not specify behavior that is important to real-time developers. Though the Real-Time Specification for Java (RTSJ) [6] improves upon standard edition semantics, it still leaves many aspects of threading behavior imprecisely specified and/or implementation defined. This hinders software reuse and adds complexity and costs to software maintenance activities. This paper suggests an alternative approach that improves portability and efficiency, without sacrificing important analyzability and generality requirements. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
INDEX TERMS
Primary Classification:
Additional Classification:
General Terms:
Keywords:
|
|||||||||||||||||||||||||||||||||||||||||||