Comments on: C++ Typecasting Part 2 – RTTI, dynamic_cast, typeid and type_info

By: ABDUL

ABDUL — Thu, 08 Dec 2011 04:44:27 +0000

SOOOOOOOOOOOOOOOOOOOOPPPPEEER!!

By: yathri

yathri — Fri, 07 Oct 2011 17:04:25 +0000

its super but need more information thanks

By: Amu

Amu — Mon, 09 May 2011 06:18:45 +0000

how exactly typeid is returning type_info&?.. In the type_info class constructor is in private mode..

By: Sonia

Sonia — Fri, 29 Apr 2011 15:03:43 +0000

i like this detail explanation.thanks

By: Anish Jain

Anish Jain — Sat, 05 Mar 2011 09:41:18 +0000

i like it man ….

By: shilpa

shilpa — Sat, 20 Nov 2010 20:27:07 +0000

thanks for this explanation.i am searched many websites but i have not get like this point detail explanation.

By: admin

admin — Mon, 07 Jun 2010 21:18:42 +0000

Yes, you are right, dynamic_casts comes at a price. A good rule is to do type checking that can take place at compile time than at run-time. Further more early type checking ensures faster execution time and in most cases a smaller executable. (Also in most cases, early type checking ensures early error detection, this can be even more important than the previous two!) But you should never overdo dynamic_casts! So if you find yourself using dynamic_cast extensively, you should always take another look at your applications design.

By: Kumar Santosh

Kumar Santosh — Mon, 07 Jun 2010 10:22:51 +0000

dynamic_cast comes at price, so one should be moderate in choosing the typeid and dynamic_cast. because, dynamic_cast has to traverse the entire hierarchy to determine the type of the object.