Access the full text.
Sign up today, get DeepDyve free for 14 days.
References for this paper are not available at this time. We will be adding them shortly, thank you for your patience.
The abort statement is used to bring about the unconditional completion of one or more tasks. However, some tasks are not required to become complete immediately upon execution of the abort statement and can continue to execute, perhaps indefinitely. While the use of forced synchronization points will bring about the completion of such tasks, they can produce undesirable run-time behavior in "normal" tasks. This paper presents an alternative to unconditional forced synchronization that allows abnormal tasks to become complete, but does not interfere with normal tasks.
ACM SIGAda Ada Letters – Association for Computing Machinery
Published: Sep 1, 1989
Read and print from thousands of top scholarly journals.
Already have an account? Log in
Bookmark this article. You can see your Bookmarks on your DeepDyve Library.
To save an article, log in first, or sign up for a DeepDyve account if you don’t already have one.
Copy and paste the desired citation format or use the link below to download a file formatted for EndNote
Access the full text.
Sign up today, get DeepDyve free for 14 days.
All DeepDyve websites use cookies to improve your online experience. They were placed on your computer when you launched this website. You can change your cookie settings through your browser.