🚀 go-pugleaf

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.

The rule of thumb I've been told is not to use RTTI unless there's 
just no other way to do it.


-- 
#include <legalbs/standarddisclaimer>
Rich Paul                |  If you like what I say, tell my
C++, OOD, OOA, OOP,      |  employer, but if you don't,
OOPs, I forgot one ...   |  don't blame them.  ;->
---
[ 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 
]