From -4601360086803567857
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f78e5,fbd36da46c3cc7a0
X-Google-Attributes: gidf78e5,public
From: "James Kuyper Jr." <kuyper@wizard.net>
Subject: Re: Discussion: type_info
Date: 1999/11/26
Message-ID: <383C81FC.C9ACD7E@wizard.net>#1/1
X-Deja-AN: 553253490
Approved: Fergus Henderson <fjh@cs.mu.oz.au>, moderator of comp.std.c++
Content-Transfer-Encoding: 7bit
References: <81ecdl$pq$1@nnrp1.deja.com> <MPG.12a60bdb1a6972e79896fb@news.teleport.com>
X-Accept-Language: en,de,es,ru
X-Relay-IP: 128.250.1.22
X-Authentication-Warning: mulga.cs.mu.OZ.AU: fjh set sender to devnull@stump.algebra.com using -f
Content-Type: text/plain; charset=us-ascii
X-Trace: typ12.nn.bcandid.com 943489457 206.161.15.49 (Wed, 24 Nov 1999 19:24:17 EST)
Organization: Not Enough
X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov)
MIME-Version: 1.0
NNTP-Posting-Date: Wed, 24 Nov 1999 19:24:17 EST
Newsgroups: comp.std.c++

Scott Meyers wrote:
....
> Just for the record, I don't think it's out for the design I sketch in
> the MEC++ errata, because it's okay to specialize less for
> pair<const type_info*, const type_info*>, which is the type I propose
> putting into the map.  That is, I agree that you can't specialize std::less
> for a pointer type, but I believe you can specialize it for a std::pair
> containing pointer types.

17.4.3.1 p1: "... Such a specialization ... results in undefined
behavior unless the declaration depends on a user-defined name of
external linkage ..."

I didn't see any user-defined names in your example.

---
[ 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              ]




