Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!hsdndev!think.com!sdd.hp.com!uakari.primate.wisc.edu!aplcen!aplcomm!uunet!cme!cam!ARTEMIS
From: miller@FS1.cam.nist.gov (Bruce R. Miller)
Newsgroups: comp.lang.c++
Subject: Re: Virtual things, lists, collections, ...
Message-ID: <2886162323@ARTEMIS.cam.nist.gov>
Date: 17 Jun 91 15:45:23 GMT
References: <38@tdatirv.UUCP>
Sender: news@cam.nist.gov
Followup-To: comp.lang.c++
Organization: NIST - Computing and Applied Mathematics Laboratory
Lines: 16


In article <38@tdatirv.UUCP>, Stanley Friesen writes: 
> In article <2885836642@ARTEMIS.cam.nist.gov> miller@FS1.cam.nist.gov (Bruce R. Miller) writes:
> >Just how is it that Virtual functions work?  ie. Where's the type info
> >at run type stored.  Do the objects have (hidden) headers?
> ...
Thanks for the info.

> Now, remember - DO NOT RELY ON THIS IMPLEMENTATION - it is NOT guarenteed.

and thanks for the reminder.

I wasn't really interested in _Using_ the information to hack up mystery
code.  But to try to understand what C++ `typically` does with a
program.  Given all the options in C++, I need a better model of what
goes on underneath to choose the `best' way to code foo.