From -384572399501070436 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,fbd36da46c3cc7a0 X-Google-Attributes: gidf78e5,public From: "TiTi" Subject: Re: Discussion: type_info Date: 1999/11/29 Message-ID: <81tdvj$i7i$1@trex.antw.online.be>#1/1 X-Deja-AN: 554496911 X-NNTP-Posting-Host: gateway.ds.adpbenelux.com Approved: stephen.clamage@sun.com (comp.std.c++) References: <81ecdl$pq$1@nnrp1.deja.com> X-UID: 0000000001 X-Priority: 3 X-Status: $$$T X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2918.2701 Organization: Customer of Online Internet X-MSMail-Priority: Normal Newsgroups: comp.std.c++ Originator: clamage@taumet > Recall also that the STL doesn't provide hashing anywhere, as far as I can see. Type_info is being consistent with that. >When hashing gets added, as I hope it will be in 5 or 10 years time, it will presumably come with a > bunch of conventions about the name of the hash function, the type of the > hashed value, etc. Type_info is right to avoid pre-empting those > decisions. Are you out of your mind? 5 to 10 years, for something that should have been in in the first place? Then I don't think that you use it very often. I used it in Java, SmallTalk & C++, over the last 5 years, and I could not have done things so fast without 'em. 5 to 10 years? I can't believe it!! TiTi PS: you ruined my day (but it's only monday ...) [ 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 ]