Find out type of class

[je-wo]

How do I find out, which type of class the variable is, I catually have.

Let me give you an example how I mean this:

CRectangle* rectangle =  new CRectangle();
if (   isClassType(CRectangle, rectangle)    )
{
          print("the variable rectangle is a CRectangle class");
}

The function I search has another name and other variables, but it finds out, what kind of class the variable (or pointer) is.

I know there is a function like the isClassType() in MFC, but I don`t find it.
Please help.

[Ejaz]

Is typeid what you looking for?

[VictorN]

MFC: CObject::IsKindOf

Also, take a look at GetClassName API

[marsh_pottaye]

All-in-one HERE.

[je-wo]

MFC: CObject::IsKindOf

Thanks, that`s it. It`s working fine.

[Hokutata]

MFC: CObject::IsKindOf

Also, take a look at GetClassName API

What is the connection between CObject::IsKindOf and GetClassName API

[Paul McKenzie]

How do I find out, which type of class the variable is, I catually have.

Let me give you an example how I mean this:

CRectangle* rectangle =  new CRectangle();
if (   isClassType(CRectangle, rectangle)    )
{
          print("the variable rectangle is a CRectangle class");
}

Anytime you need to code like this, think about how you've designed the program. More often than not, there is a flaw in your design.

In C++, you have virtual functions, and the need for doing this is for the most part, unnecessary.

Regards,

Paul McKenzie

[VictorN]

What is the connection between CObject::IsKindOf and GetClassName API

AFAIK, there is no connection between them.
They work independently and return different values/value types.

[TheCPUWizard]

As Paul pointed out, C++ was deliberately designed (originally) to NOT provide run-time type identification. Later versions of the language do support RTTI (it is necessary internally for dynamic_cast). The MFC classes (derived from CObject) have their own methodology. COM classes have a different methodogy.

Think (and think again) if you really need to make use of any of the available methods. At the very least it will potentially decrease the portability of your code if you use them [actually if you do use MFC or COM you have already reduced the portability of your code ]