home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.lang.c++:12424 comp.std.c++:1086
- Newsgroups: comp.lang.c++,comp.std.c++
- Path: sparky!uunet!sybus.sybus.com!myrddin!tct!chip
- From: chip@tct.com (Chip Salzenberg)
- Subject: Re: run-time type checking, freezing, and thawing
- Message-ID: <2A8FAA88.8ED3@tct.com>
- Date: Mon, 17 Aug 1992 13:32:56 GMT
- References: <SRS56GM@netmbx.netmbx.de> <2A827EAE.6AEE@tct.com> <T6W55ZU@netmbx.netmbx.de>
- Organization: TC Telemanagement, Clearwater, FL
- Lines: 20
-
- According to jrobie@netmbx.netmbx.de (Jonathan Robie):
- >chip@tct.com (Chip Salzenberg) writes:
- >>According to jrobie@netmbx.netmbx.de (Jonathan Robie):
- >>>Well, the full polymorphic type should contain precisely the information
- >>>found in the class declarations, no more and no less.
- >
- >>Yes, but is that the >>C++<< class declaration, or the >>POET<< class
- >>declaration?
- >
- >The C++ class declaration, of course.
-
- But a C++ doesn't provide enough information for persistence. That's
- why POET has the "transient" keyword, for example. So the "complete
- polymorphic type information" required for thawing an object is _not_
- the C++ type information, but rather the POET type information (though
- the latter is a superset of the former, to be sure).
- --
- Chip Salzenberg at Teltronics/TCT <chip@tct.com>, <73717.366@compuserve.com>
- "Do Rush place weird subliminal backmasked messages in their songs to
- compel unwilling geeks to commit evil .sig atrocities?" -- Dean Engelhardt
-