Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!know!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!psuvax1!rutgers!cunixf.cc.columbia.edu!cs.columbia.edu!read.columbia.edu!kearns
From: kearns@read.columbia.edu (Steve Kearns)
Newsgroups: comp.lang.c++
Subject: Re: persistence
Message-ID: <1990Sep25.235837.27351@cs.columbia.edu>
Date: 25 Sep 90 23:58:37 GMT
References: <995@halley.UUCP> <CLINE.90Sep25002931@cheetah.ece.clarkson.edu>
Sender: news@cs.columbia.edu (The Daily News)
Reply-To: kearns@cs.columbia.edu
Organization: Columbia University Department of Computer Science
Lines: 18

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.