From 5127701920641241258 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,fbd36da46c3cc7a0 X-Google-Attributes: gidf78e5,public From: "James Kuyper Jr." Subject: Re: Discussion: type_info Date: 1999/12/08 Message-ID: <384DB1F7.D5844840@wizard.net>#1/1 X-Deja-AN: 558213782 X-NNTP-Posting-Host: 209.8.153.6 Content-Transfer-Encoding: 7bit Approved: stephen.clamage@sun.com (comp.std.c++) References: <81ecdl$pq$1@nnrp1.deja.com> <81u646$kln$1@nnrp1.deja.com> <823n5t$7qg@library1.airnews.net> <384BBE4F.ABDC393C@lucent.com> <7QYbIRArmTT4Ew2J@robinton.demon.co.uk> <82ju8c$jbf$1@oak.prod.itd.earthlink.net> X-Accept-Language: en,de,es,ru X-UID: 0000000001 X-Status: $$$T Content-Type: text/plain; charset=us-ascii X-Trace: typ11.nn.bcandid.com 944615761 209.8.153.6 (Tue, 07 Dec 1999 20:16:01 EST) Organization: Not Enough Mime-Version: 1.0 NNTP-Posting-Date: Tue, 07 Dec 1999 20:16:01 EST Newsgroups: comp.std.c++ Originator: clamage@taumet Francis Glassborow wrote: .... > There is no problem with comparing pointers for equality (even without > normalisation) however requiring that less than shall always 'work' is > requiring a complete ordering of addresses and that is something else. std::less is required to yield a total order, even if the built-in 'operator<' doesn't. Thus, the necessary work has already been done by the implementation. Unfortunately, even though there's almost certainly something associated with each pointer that could be used to hash it, the standard doesn't require implementations to make that something available to users. [ 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 ]