Persistent First Class Procedures are Enough
Proceedings of the Fourth Conference on Foundations of Software Technology and Theoretical Computer Science
Programming with abstract data types
Proceedings of the ACM SIGPLAN symposium on Very high level languages
Some desirable properties of data abstraction facilities
Proceedings of the 1976 conference on Data : Abstraction, definition and structure
Procedural encapsulation: A linguistic protection technique
Proceeding of ACM SIGPLAN - SIGOPS interface meeting on Programming languages - operating systems
The string as a simple data type
ACM SIGPLAN Notices
Types and persistence in database programming languages
ACM Computing Surveys (CSUR)
Collaboration and composition: issues for a second generation process language
ESEC/FSE-7 Proceedings of the 7th European software engineering conference held jointly with the 7th ACM SIGSOFT international symposium on Foundations of software engineering
Using persistence technology to control schema evolution
SAC '94 Proceedings of the 1994 ACM symposium on Applied computing
Orthogonally persistent object systems
The VLDB Journal — The International Journal on Very Large Data Bases - Persistent object systems
Hi-index | 0.00 |
The software engineering community has recognised the need for integrated project support environments (IPSEs) for some time. The technique of integration as a method of cost saving applies to all levels in the hierarchy of problem solving, both hardware and software. This paper discusses one such level, that in which the IPSE is implemented and in particular the use of a persistent store as an enabling technology for IPSEs.The facilities of the language PS-ALGOL necessary to support an IPSE are illustrated by example and it is demonstrated how an IPSE's base may be provided by a persistent store that supports first class procedures as data objects. The need for a type secure object system which allows static and dynamic binding is demonstrated and finally the secure transactional base of PS-ALGOL is shown to be a necessary and sufficient condition to provide secure version control and concurrent access to both programs and data.