Path: utzoo!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!pdn!tscs!tct!chip
From: chip@tct.uucp (Chip Salzenberg)
Newsgroups: comp.lang.c++
Subject: Re: asking an object for its type
Message-ID: <27D7F621.2F5@tct.uucp>
Date: 8 Mar 91 20:37:53 GMT
References: <27D57565.2B22@tct.uucp> <1991Mar7.153417.6489@linus.mitre.org> <1991Mar8.024331.14235@searchtech.com>
Organization: Teltronics/TCT, Sarasota, FL
Lines: 19

According to johnb@searchtech.com (John Baldwin):
>Perhaps what we have here is in fact a needed extension to the language
>which, when not used judiciously, can be harmful.

I would agree, except for the "needed" part.  :-/

>Here's the real question: has anyone here needed type testing *for ANY
>other reason* than,
>      1) to implement persistent objects, or
>      2) to allow run-time object selection?

I still haven't been shown why type testing is so important for
persistent object creation.  In other words, as an implementor of
persistent objects, what does isKindOf() do for you that virtual
functions can't or shouldn't?
-- 
Chip Salzenberg at Teltronics/TCT     <chip@tct.uucp>, <uunet!pdn!tct!chip>
 "Most of my code is written by myself.  That is why so little gets done."
                 -- Herman "HLLs will never fly" Rubin