From -8000584372968238952 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,206db806b836bf67 X-Google-Attributes: gidf78e5,public From: chelly@eden.com (Chelly Green) Subject: Re: Pointers to incomplete type Date: 1998/01/29 Message-ID: #1/1 X-Deja-AN: 320342402 Content-Transfer-Encoding: 8bit References: <69osom$jf3@examiner.concentric.net> <6a0a4g$rf1@shell.magma.ca> <6a0t54$k83@examiner.concentric.net> X-Original-Date: Tue, 20 Jan 1998 22:01:23 -0600 Content-Type: text/plain; charset=ISO-8859-1 Organization: - X-Auth: PGPMoose V1.1 PGP comp.std.c++ iQBVAwUBNNDTYEy4NqrwXLNJAQEeugH/YTsN7HJz/xprVkztrGY8XZtBLrzm+SEl MEBZS1Fwes+6td2iCTctxyp6GHntEKpZSNlz4hUklFJDCclNKW87yg== =jE6/ Newsgroups: comp.std.c++ Originator: austern@isolde.mti.sgi.com In article <6a0t54$k83@examiner.concentric.net>, "Bradd W. Szonye" wrote: > [put vtable ptr in every pointer to object instead of object itself] > ... > Now, hopefully I've convinced you that the "alternate" object model is worth > considering even if it's not ideal for all applications. The question > remains, can you implement "fat" polymorphic pointers without burdening all > the non-polymorphic pointers with a vptr? The real question is, can you implement them at all? When an object's type changes, how do all pointers to it get their vtable pointer updated? When does an object's type change, you ask? Well, every time a derived class constructor/base class destructor executes. -- Chelly Green | chelly@eden.com | C++ - http://www.eden.com/~chelly --- [ comp.std.c++ is moderated. To submit articles: Try just posting with your newsreader. If that fails, use mailto:std-c++@ncar.ucar.edu comp.std.c++ FAQ: http://reality.sgi.com/austern/std-c++/faq.html Moderation policy: http://reality.sgi.com/austern/std-c++/policy.html Comments? mailto:std-c++-request@ncar.ucar.edu ]