CObject Class

Question

4.50/5 (6 votes)

See more:

C++

MFC

Why is CObject the base class for the majority of MFC classes?

Posted 12-Jul-10 22:09pm

Pryabu

Updated 13-Jul-10 6:17am

Nish Nishant

v2

Add a Solution

4 solutions

Solution 3

What difference does it make *-why* CObject is the ultimate base class. It simply is, and there's nothing you can do about it.

Posted 13-Jul-10 1:50am

#realJSOP

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Eugen Podsypalnikov · Accepted Answer · 2010-07-14T05:16:00

Solution 4

From CObject Class (MFC)[^] on MSDN:

CObject provides basic services, including:
- Serialization support
- Run-time class information
- Object diagnostic output
- Compatibility with collection classes

...it could be venerated :)

Posted 14-Jul-10 5:16am

Eugen Podsypalnikov

Updated 14-Jul-10 5:22am

v2

Aescleal · Accepted Answer · 2010-07-12T23:45:00

Simple answer - it's not.

The answer to "why did Microsoft think it was a good idea in MFC to derive (almost) everything from CObject?" is probably that they thought it was a good idea at the time.

Back in 1991 the C++ implementation they had to play with was a pretty unsophisticated C++ compiler (no templates, namespaces and exceptions) and some of the features of CObject were really to overcome the lack of features and lack of experience of using C++. This includes things like dynamic creation and base class pointer collection classes.

Cheers,

Ash

CPallini · Accepted Answer · 2010-07-12T22:31:00

Solution 1

What is the point of your question?
Are you asking about the usefulness of a single rooted classes hierarchy?
Are you asking if CObject fits well as MFC root class?
Or are you worried about "CObject" as root class name?
:)

Posted 12-Jul-10 22:31pm

CPallini

Comments

Nish Nishant 13-Jul-10 12:15pm

Reason for my vote of 5
Good answer, and worth a 5!