More rtti queries

[Jim Dehnert]

More feedback from the meeting:

> From: Nathan Sidwell <sidwell at codesourcery.com>
> 
> 1)
> Am I just having a thinko, but when would a type_info of a reference
> ever be generated? (So why __ref_type_info?)
> 
> typeid(T) will strip the reference [expr.typeid]/4
> a thrown type will never be a reference, [except.throw]/3
> a catch type ignores a reference [expr.handle]/3
> an exception specification can contain a reference, but behaves the same
> as a catch would. [except.spec]

Concern  remains that we may need to deal with pointers to ref
members.

> 2)
> Is __ptr_to_member_type_info for just member data, or both member data
> and member functions. The standard uses `pointer to member' to mean
> `pointer to member data', but given the inconsistency which as popped
> up with polymorphic, I'm not sure. It's also named inconsistently to
> __pointer_type_info, and might be considered a subclass of that :-)

I have fixed the spelling.  Someone at the meeting claims that the
standard uses `pointer to member' to mean both `pointer to member data'
and `pointer to member function'.

> nathan
> -- 
> Dr Nathan Sidwell :: sidwell at codesourcery.com
> nathan at acm.org  http://www.cs.bris.ac.uk/~nathan/  nathan at cs.bris.ac.uk
> 
-	    Jim Dehnert		dehnert at sgi.com
				(650)933-4272