🚀 go-pugleaf

Rich Paul wrote:
> 
> Satrajit Sujit Ghosh wrote:
> >
> >         Would it be possible to illustrate efficient, convenient and
> > pratical use of the RTTI functions?
> >
> 
> Hmmm ... well, this comes in handy:
> 
> ostream &operator << ( ostream &os, const exception &e )
> {
>         return os << endl
>                   << "Exception: " << typeid(e).name() << endl
>                   << "Message:   " << e.what() << endl;
> };
> 
> Since the typename of the exception carries some of the most relevent
> information about the exception, why not use it ... of course, the
> same thing could be done with virtual functions.
> 

Except that typeid(e).name() returns an implementation-defined value which ( 
if my reading of the April DWP is correct ) is not necessarily a 
null-terminated string. It might even be an invalid pointer so that the above 
function wouldn't work at all. I don't know if this has already been done but 
if not - why not guarantee that the pointer is at least valid?

Bye

Roman
---
[ comp.std.c++ is moderated.  To submit articles: Try just posting with your 
                newsreader.  If that fails, use mailto:std-c++@ncar.ucar.edu
  comp.std.c++ FAQ: http://reality.sgi.com/austern/std-c++/faq.html
  Moderation policy: http://reality.sgi.com/austern/std-c++/policy.html
  Comments? mailto:std-c++-request@ncar.ucar.edu 
]