Abstract
Interference is what makes the design of concurrent programs difficult. In the case of shared-variables, interference manifests itself as state changes; but the issue of interference is also present with communication-based concurrency. In order to reason about interfering programs it is necessary to assume something about the granularity of the steps of the processes concerned. Many development methods circumvent this difficulty by fixing which statement types are atomic. It can be argued that this is unfortunate and is likely to result in programs which are inefficient (in a particular way). This extended abstract shows how development methods based on rely/guarantee-conditions avoid a commitment to a fixed notion of atomicity and suggests that concurrent object-oriented languages are good targets for such a development method.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
