"Rob Williscroft" <rtw@freenet.co.uk> wrote in message
news:Xns953C85BEF8BA8ukcoREMOVEfreenetrtw@130.133. 1.4...[color=blue]
> Kleidemos wrote in news:TDoQc.75072$OR2.4257914@news3.tin.it in
> comp.lang.c++:
>[color=green]
> > Rob Williscroft wrote:[color=darkred]
> >>
> >> Before you "re-implement" RTTI what's your problem with the language
> >> features (that are always present BTW) commonly refered to as RTTI ?[/color]
> >
> > It's, IMHO, more Os dipendent and more complicate and wrong
> > implementated than how it could be.
> >
> >[/color]
>
> Ok, what dosen't it do that you want ?.
>
> AFAICT you code solved the problem that:
>
> typeid( <object-reference> ).name()
>
> return's an implementation defined "string", but it imposes that *every*
> object be polymorphic. In effect its a variation of "everything is an
> `Object` (i.e. is-a/derived from)" systems (as in jave/c# etc) that
> have been tried and abandoned countless times:[/color]
Microsoft's MFC uncannilly similar implementation demonstrates your point
very well.
[color=blue]
> Perhapse you will find:
>
>
http://lists.boost.org/MailArchives/boost/msg64112.php
>
> (subject "[boost] typeof")
>
> interesting.[/color]
What purpose does the OP anticipate using this 'facility' to accomplish?
IIRC, the only uses for RTTI are serialization and multiple dispatch. In
which case boost::serialization should be of interest as well at
www.rrsd.com. Certainly C++ RTTI is sufficient for MultipleDispatch examples
that I've seen to date.
Jeff F