Xref: utzoo comp.object:2446 comp.lang.pascal:5268
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!samsung!think.com!paperboy!hsdndev!husc6!genrad!genrad.com!mas
From: mas@genrad.com (Mark A. Swanson)
Newsgroups: comp.object,comp.lang.pascal
Subject: Re: Shouldn't debuggers be able to debug dynamic objects?
Summary: Program frameworks can support debug by using object design reqs
Message-ID: <40541@genrad.UUCP>
Date: 28 Jan 91 20:57:20 GMT
References: <1991Jan24.152256.24273@resam.dk> <1991Jan25.145947.16431@bellcore.bellcore.com> <1991Jan28.100213.1822@resam.dk> <1991Jan28.151241.25449@bellcore.bellcore.com>
Sender: news@genrad.UUCP
Reply-To: mas@crom.genrad.COM (Mark A. Swanson)
Followup-To: comp.object
Distribution: comp
Organization: GenRad, Inc., Concord, Mass.
Lines: 8

Determining what a dynamic object is is not always possible in raw C++.
However, if one is developing within a development environment with a standard
set of object coding conventions (e.g. a required char *myclass() method)
an integrated debugger can use them to provide such functionality.

Such a layered approach is practical now and avoids having to wait years
for invention and agreement on how best to support meta-identities without
adding to C++'s minimal object overhead.