| A. Albano, G. Ghelli, and R. Orsini. The Implementation of Galileo's Persistent Values, chapter 16, pages 253--263. Springer-Verlag, 1988. |
....of these languages provide the software engineer with the ability to constrain the effects of evolving an application in the way DRASTIC s zones and zone contracts do. 8. 6 Persistent Languages Type evolution is more of a problem for programming languages that support persistence [DCBM89, MMM93, AGO88, AJDS96] than for those that do not. This is because the persistent store contains data which is loaded into type instances at run time. If a type is changed, instances of that type may not longer be retrievable from the store unless some form of transformation is performed. This can lead to the ....
A. Albano, G. Ghelli, and R. Orsini. The Implementation of Galileo's Persistent Values, chapter 16, pages 253--263. Springer-Verlag, 1988.
....prototype object oriented systems have been built, often emphasising different facets of the overall functionality. For example, systems such as Argus [14] Arjuna [11, 23, 29] SOS [28] and Guide [4] have emphasised fault tolerance and distribution aspects, languages such as PSAlgol [3] Galileo [2] and E [25] have contributed to our understanding of persistence as a language feature, while efforts such as [12] have contributed to the understanding of the design of object stores and their relationship to database systems. We build on these efforts and describe the necessary features of a ....
Albano, A., Ghelli, G., and Orsini, R., "The Implementation of Galileo's Persistent Values", in Data Types and Persistence, Atkinson, M.P., Buneman, P., and Morrison, R. (eds.) , Springer-Verlag, 1988, pp. 253263.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC