Skip Navigation

The Computer Journal 1981 24(4):331-338; doi:10.1093/comjnl/24.4.331
© 1981 by British Computer Society
This Article
Right arrow Full Text (PDF)
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Similar articles in ISI Web of Science
Right arrow Alert me to new issues of the journal
Right arrow Add to My Personal Archive
Right arrow Download to citation manager
Right arrowRequest Permissions
Google Scholar
Right arrow Articles by Hopper, K.
Right arrow Search for Related Content
Social Bookmarking
 Add to CiteULike   Add to Connotea   Add to Del.icio.us  
What's this?

Retained objects and operating system interfaces

K. Hopper *

Department of Computer Studies, University of Leeds, Leeds, LS2 9TJ, UK

The general nature of all types of object which a user may wish to retain between computing sessions is shown to be that of a file. The requirement that a transportable control language provide identical semantic effects everywhere leads to the idea of a universal file system. The specification of a file in such a system is discussed before considering the effects of widely varying underlying file systems on the mappings and facilities needed in a control language processor to support such a universal file system. Discussion of file manipulations and network connection requirements completes the design requirements for the use of retained objects in a control language processor.


Received February 1980.

* Department of Computer Studies, University of Leeds, Leeds, LS2 9TJ, UK


Add to CiteULike CiteULike   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us    What's this?




Disclaimer:
Please note that abstracts for content published before 1996 were created through digital scanning and may therefore not exactly replicate the text of the original print issues. All efforts have been made to ensure accuracy, but the Publisher will not be held responsible for any remaining inaccuracies. If you require any further clarification, please contact our Customer Services Department.