1. With the advantages of C + +, MFC opens up a new world for Windows development, while also leveraging Applicationwizzard to get developers out of those basic code that must be written every time.
2. ClassWizard and message maps enable developers to get rid of the messy and lengthy code snippets that define message handling.
3. Even more exciting is the use of the C + + encapsulation feature that allows developers to get rid of the various handles in Windows, only to face objects in C + +, so that development closer to the development of language and away from the system. (But I personally think that understanding the system principle is very helpful for development). Because MFC is based on C + +, I emphasize the importance of the C + + language foundation for development:
1) using C + + packaging developers can more easily understand and manipulate various window objects;
2) The use of C + + derived developers can reduce the time to develop custom windows and create reusable code;
3) The use of virtualization can better control the activity of the window when necessary.
4) and C + + itself has the ability to go beyond the C language to enable developers to write more easily and more flexible code.
Reference (includes message map and learning method Summary):
Http://www.cnblogs.com/bingcaihuang/archive/2010/12/02/1894062.html
Summary: It is the class object in place of the handle for a variety of operations, easy to manage, but also inherited/overwritten/reused, that's all. In reading Delphi source code, many times found that through the Delphi Object Management window than through the management of the handle more convenient, the handle is nothing, but one of the many properties of Delphi object. And I also found that sometimes it is necessary to find the object through a handle, so that it is easy to operate and fully manage.
Again, the class object is very powerful, almost arbitrary and omnipotent, and the handle is just one of the properties used to manage the window.
The oo thinking of VC + +