kearns@read.columbia.edu (Steve Kearns) (09/26/90)
In article <CLINE.90Sep25002931@cheetah.ece.clarkson.edu> cline@sun.soe.clarkson.edu (Marshall Cline) writes: >Not to sound like I'm double minded or anything, but Keith Gorlen's NIHCL >does a wonderful job of providing persistent objects. Ideally persistence >should be buried in the language so as to avoid the temptation to check the >type of an object at runtime for other purposes as well (it may sound >trivial, but: you only need to check the type of a referenced object when >you don't know the type, and that implies you're relying on weak typing). I >wish C++ proper gave us persistence; that way no one would have to pay the >horrible prices imposed by Smalltalk-like C++ libraries. > The following article has an excellent discussion of 1 way to integrate persistence into c++: Joel E. Richardson, Michael J. Carey, Persistence in the E Language: Issues and Implementation, Software-Practice and Experience, 19(2), December 1989, pp. 1115-1150.