From 2854612906268265056 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,fbd36da46c3cc7a0 X-Google-Attributes: gidf78e5,public From: Gene Bushuyev Subject: Re: Discussion: type_info Date: 1999/12/20 Message-ID: <83kjmg$cru$1@nnrp1.deja.com>#1/1 X-Deja-AN: 563111791 X-NNTP-Posting-Host: 63.23.195.13 Approved: stephen.clamage@sun.com (comp.std.c++) References: <82gmer$gqm$1@nnrp1.deja.com> <384c8866.77375470@news.internetconnect.net> <82lv69$atk$1@nnrp1.deja.com> <3855bd24.78125498@news.internetconnect.net> X-UID: 0000000001 X-Status: $$$T X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT) X-Http-Proxy: 1.1 x28.deja.com:80 (Squid/1.1.22) for client 63.23.195.13 Organization: Deja.com - Before you buy. X-Article-Creation-Date: Mon Dec 20 06:52:00 1999 GMT X-MyDeja-Info: XMYDJUIDgbush Newsgroups: comp.std.c++ Originator: clamage@taumet In article , Alan Hadsell wrote: [snip] > > The compiler can't tell when it's compiling a class whether it needs > to generate its type_info, because it doesn't necessarily know whether > anyone will use typeid() on it. It doesn't need to generate the type_info per se. It can generate a code to produce type_info on demand. [snip] > So only the linker has enough information to decide whether to include > a particular type_info object, and it can only do so if it can > determine the set of all types that might be returned from all > typeid() calls in the program. Does the standard say anything about the existance of a linker? This division is the heritage of the past I hope we are seeing the end of it. ------------------------------------- Gene Bushuyev Sent via Deja.com http://www.deja.com/ Before you buy. [ comp.std.c++ is moderated. To submit articles, try just posting with ] [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html ]