home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: sparky!uunet!mcsun!Germany.EU.net!news.netmbx.de!netmbx!jrobie
- From: jrobie@netmbx.netmbx.de (Jonathan Robie)
- Subject: Re: run-time type checking, freezing, and thawing
- Organization: netmbx, Berlin, Germany
- Date: Wed, 12 Aug 1992 13:43:05 GMT
- Message-ID: <WNZ5RGC@netmbx.netmbx.de>
- References: <2A7FCE77.45E5@tct.com> <IRS5BBM@netmbx.netmbx.de> <2A827DFD.6D68@tct.com> <1992Aug10.191631.4133@microsoft.com>
- Lines: 34
-
- jimad@microsoft.com (Jim Adcock) writes:
-
- >In article <2A827DFD.6D68@tct.com> chip@tct.com (Chip Salzenberg) writes:
- >|Therefore, EVEN IF the C++ standard includes RTTI, object storage will
- >|STILL require preprocessors and all that loathsome junk that you claim
- >|will be unnecessary once RTTI becomes available.
-
- >An alternative to loathsome preprocessors is to use loathsome postprocessors
- >instead and grovel over the debugging information emitted in the .objs.
- >This makes your postprocessors dependent on the .obj format emitted, but
- >still this should be an easier task.
-
- We could take that even one step further, and grovel over debugging info
- placed in the .EXEs. In fact, we could develop a general purpose library
- for accessing this information. And we could standardize this for all
- vendors. We have now rederived the concept of extended run time type
- information....
-
- Jonathan
-
- ========================================================================
-
- Jonathan Robie jrobie@netmbx.UUCP
- Arnold-Zweig-Str. 44 jrobie@netmbx.in-berlin.de
- O-1100 Berlin
- Deutschland Phone: +37 (2) 472 04 19 (Home, East Berlin)
- +49 (30) 342 30 66 (Work, West Berlin)
-
-
- --
- Jonathan
-
- ===========================================================================
-
-