From -4350619225147402085 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,5cc0e5689db82f7b X-Google-Attributes: gidf78e5,public From: Hubert HOLIN Subject: Re: Is type_info object static or temporary? Date: 1998/06/15 Message-ID: <3585024E.7E3B1CD4@ArtQuest.fr>#1/1 X-Deja-AN: 362859924 Content-Transfer-Encoding: 7bit Approved: stephen.clamage@sun.com (comp.std.c++) References: <35727d32.0@210.134.196.10> <6kvbv8$o6@engnews1.Eng.Sun.COM> <3580C202.10C45BA@ix.netcom.com> <6lurbs$7tl$1@nnrp1.dejanews.com> Mime-Version: 1.0 Reply-To: Hubert.Holin@Bigfoot.com Originator: clamage@taumet X-NNTP-Posting-Host: ns.artquest.fr X-UID: 0000000001 X-Status: $$$T Content-Type: text/plain; charset=us-ascii Organization: ArtQuest Newsgroups: comp.std.c++ Paris (U.E.), le 15/06/1998 AllanW@my-dejanews.com wrote: [SNIP] > It does remind me of a different suggestion I recently heard, though, about > having a compliant compiler that deliberately does things differently, in > order to quickly flag compatibility problems in code that may happen to work > locally. There are already real compilers that do this for the limited > problem of memory allocation -- i.e. overwriting deleted data with a pattern > or making it inaccessible. > > Doing this for every documented C++ feature seems to be a much bigger > problem, perhaps infeasible. I suppose such a compiler would have to > twist the RTTI as far as possible; perhaps even by returning class names > that can't be easily mapped to the source code names; i.e. at runtime > select a unique but random combination of letters and digits. Then on > one particular run, the name of int might be "X1", the name of long might > be "3UR23", the name of class istream might be "3UR2", etc.! [SNIP] I would definitely welcome such a tool! Not only would it be great for testing portability, but it would also allow one to be fiendish in the classroom :-) ! Hubert Holin Hubert.Holin@Bigfoot.com [ 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 ]