ACM Home Page
Please provide us with feedback. Feedback
Digital Library logoTake a look at the new version of this page: [ beta version ]. Tell us what you think.
Deadlock control with Ada95
Full text PdfPdf (509 KB)
Source ACM SIGAda Ada Letters archive
Volume XVIII ,  Issue 2  (March/April 1998) table of contents
Pages: 67 - 80  
Year of Publication: 1998
ISSN:1094-3641
Author
Trudy Levine  Fairleigh Dickinson University, Teaneck, NJ
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 1,   Downloads (12 Months): 3,   Citation Count: 2
Additional Information:

abstract   cited by   index terms  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/279578.279596
What is a DOI?

ABSTRACT

The Ada programming language is unique in its high-level concurrency facilities, supported by a secure and powerful set of programming constructs. Ada 95 now has additional capabilities, specifically the protected type construct.Although the Ada rendezvous is prone to deadlock, a careful discipline can ensure that this type of dead state does not occur. Restricting task communication assists in preventing deadlock, yet such restrictions may be too limiting and/or too inefficient for an application. Indeed, several researchers have suggested that deadlock should not be prevented, but monitored and corrected during testing and/or run time.This paper takes the position that deadlock should be prevented by following specific guidelines in the use of the rendezvous. We define deadlock, show how it can occur with Ada tasks, and outline mechanisms that are appropriate for its control.