Adding concurrency to a statically type-safe object-oriented programming language

Buhr, Peter A.; Ditchfield, G.; Zarnke, C. Robert

doi:10.1145/67386.67389

Cited by 7 publications

(5 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…These difficulties are related to the concurrent execution of an objects's methods, and nonreentrant code. Some of these issues have been mentioned in [9]. A concurrency mechanism with multithreaded active objects must satisfactorily address the interference problem with respect to data encapsulation, procedural abstraction and reusability issues that emerge due to the potential arbitrary interleavings of an object's methods.…”

Section: Resultsmentioning

confidence: 99%

See 1 more Smart Citation

Introducing concurrency to a sequential language

Karaorman¹,

Bruno²

1993

Commun. ACM

View full text Add to dashboard Cite

INTRODUCING CONCURRENCY TO A SEQUENTIAL LANGUAGEe introduce concurrency to the object-oriented language Eiffel through a set of Class Libraries and an associated concurrent programming design method. This concurrency mechanism is well suited for client/server style distributed applications. The essential principles of sequential object-oriented programming offered by Eiffel are not sacrificed, since no changes are made to the Eiffel Language [19], or its run-time system. Our concurrency abstractions are presented as encapsulated behavior of Eiffel objects that can be inherited from the CONCURRENCY Class. Although the design described here is specific to the Eiffel language, most of these abstractions are generally applicable to other object-oriented languages such as C + + [14], and Objective-C [13].The main concurrency abstractions provided by our mechanisms are objects as processes--active objects--and an asynchronous remote method invocation with data-driven synchronization. The view of objects as processes, having a protected private state and a prescribed behavior, provides the bridge to parallelism. Also the communication/synchronization aspects of concurrent programming blend well with the method invocation model of computation in object-oriented programming.There have been numerous proposals in recent years to combine concurrent programming with object-oriented programming. We can identify three distinct approaches for introducing concurrency to object-oriented systems: Design a new concurrent object-oriented languageCOmMUN|CATmONm OP TMm ACN September 1993/Vol.36, No.9 103 C:OMMUNICATIONSOPTNIIACM Scptcmber 1993/Vol,36, No.9 SOS storage put( Item: DATA ): BOOLEAN is -do if not buffer, full then buffer.put (Item);-append to buffer Result:= true; else --return false for failure Result:= false; end; --if end; --put get: DATA is -do if not buffer.empty then buffer.remove; -remove the oldest item in buffer Result := buffer.item; -return the removed item else --return a Void object for failure Result.Forget;--Result made Void end; --if end; --get end --class BUFFER

show abstract

Section: Resultsmentioning

confidence: 99%

“…We address these issues in the section in which we present the bounded buffer example and in the conclusion to this article. Some of these issues are also addressed in [9]. The order in which we have presented the three approaches is also chronological.…”

mentioning

confidence: 99%

Introducing concurrency to a sequential language

Karaorman¹,

Bruno²

1993

Commun. ACM

View full text Add to dashboard Cite

show abstract

“…Language features such as exception handling, polymorphism, persistence and distributed programming all interact with concurrency in both obvious and subtle ways. In many cases, it is impossible for concurrency libraries to deal with these interactions, leading to imposed restrictions or coding conventions on library users that increase the potential for runtime errors (see [48,49] for those relating to C++). Again, the only way the translator can statically check for incompatible interactions among language features, so that it can print appropriate warnings and errors, are concurrency extensions.…”

Section: Concurrency = Library ‡mentioning

confidence: 99%

Concurrent urban legends

Buhr

Harji

2005

Concurrency Computat.: Pract. Exper.

View full text Add to dashboard Cite

SUMMARYThis discussion addresses a number of urban legends about concurrency in an attempt to separate the myth from the fact. These legends are as follows:1. concurrent = parallel; 2. coroutining = concurrency; 3. synchronization = mutual exclusion; 4. Dekker < Peterson; 5. concurrency = library; 6. inheritance anomaly = major concurrency problem; 7. signalling = hints; 8. spurious wakeup = efficiency.Identifying and understanding the fundamental concepts underlying concurrency is essential to the field. Equally important is not to confuse sequential and concurrent concepts. Finally, approaches based solely on efficiency are insufficient to justify a weak or difficult to use concurrent concept or construct. Copyright

show abstract

“…• Do! [183] Java//, ProActive PDC [184], see Eiffel// ¡ ¡ À À ¨¡ ¡ À Mediators [187] MeldC [188][189][190] ¡ ¡ À À ¨¡ ¡ À À Mentat [191][192][193][194][195][196] Micro C++, µC++ [198][199][200] NAM [206] ¡ ¡ À À ¨¡ ¡ À À…”

Section: Es-kit Softwareunclassified

A survey of concurrent object-oriented languages

Philippsen

2000

Concurrency: Pract. Exper.

View full text Add to dashboard Cite

SUMMARYDuring the last decade object-oriented programming has grown from marginal influence into widespread acceptance. During the same period, progress in hardware and networking has changed the computing environment from sequential to parallel. Multi-processor workstations and clusters are now quite common.Unnumbered proposals have been made to combine both developments. Always the prime objective has been to provide the advantages of object-oriented software design at the increased power of parallel machines. However, combining both concepts has proven to be notoriously difficult. Depending on the approach, often key characteristics of either the object-oriented paradigm or key performance factors of parallelism are sacrificed, resulting in unsatisfactory languages.This survey first recapitulates well-known characteristics of both the object-oriented paradigm and parallel programming, and then marks out the design space of possible combinations by identifying various interdependencies of key concepts. The design space is then filled with data points: for 111 proposed languages we provide brief characteristics and feature tables. Feature tables, the comprehensive bibliography, and web-addresses might help in identifying open questions and preventing re-inventions.

show abstract

Adding concurrency to a statically type-safe object-oriented programming language

Cited by 7 publications

References 2 publications

Introducing concurrency to a sequential language

Introducing concurrency to a sequential language

Concurrent urban legends

A survey of concurrent object-oriented languages

Contact Info

Product

Resources

About