Abstract
Many object-based and object-oriented programming languages have no way of directly preventing structural defects due to the sharing of objects. Languages such as C++, Smalltalk and Eiffel fall into the category of unsafe object languages where these defects can and do occur. This error can be prevented by use of object languages supporting safe, strong typing structures. Examples falling into this category are Ada83 and Ada95 with their limited private, strong typing and unsharable constructs. The paper shows how unsafe object sharing is prevented using these constructs. Applications where safety and security are important should be implemented using languages in this latter category.
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.
