Test environment running 7.6.6

Cultural advice

The Australian National University acknowledges, celebrates and pays our respects to the Ngunnawal and Ngambri people of the Canberra region and to all First Nations Australians on whose traditional lands we meet and work, and whose cultures are among the oldest continuing cultures in human history.

Aboriginal and Torres Strait Islander peoples are advised that ANU Library collections may include images, names, voices, and other representations of deceased persons.

Material in the collection may contain terms, language or views that reflect the period in which the item was created and may be considered inappropriate today.

Abstract and Concrete Data Types vs Object Capabilities

Thumbnail Image

Date

2018-01-01

Authors

Journal Title

Journal ISSN

Volume Title

Publisher

Abstract

The distinctions between the two forms of procedural data abstraction— abstract data types and objects—are well known. An abstract data type provides an opaque type declaration, and an implementation that manipulates the modules of the abstract type, while an object uses procedural abstraction to hide an individual implementation. The object-capability model has been proposed to enable objectoriented programs to be written securely, and has been adopted by a number of practical languages including JavaScript, E, and Newspeak. This chapter addresses the questions: how can we implement abstract data types in an object-capability language? and, how can we incorporate primitive concrete data types into a primarily object-oriented system?.

Description

Keywords

Citation

URI

https://dspace-test.anu.edu.au/handle/1885/733742388

Collections

DevOps Pure Testing

Source

Type

Chapter

Book Title

Entity type

Access Statement

License Rights

DOI

10.1007/978-3-319-98047-8_14

Restricted until

DSpace software copyright © 2002-2026 LYRASIS