WIN32 and MFC Relationship
[216 byte] By [Shiney Vang] at [2007-11-18 13:39:42] 
This might be a vague question, but what is the relationship between WIN32 and MFC programming? Is it suffice to say MFC is built on top of WIN32? Is MFC preferred over WIN32 or does WIN32 provide other advantages?
«« InputBox "resilience" for blank entries and selecting [OK] or [Cancel].
»» What control? 10 rows and 25 columns..
»» What control? 10 rows and 25 columns..
# 1 Re: WIN32 and MFC Relationship
MFC is an object oriented library that encapsulates portions of the WIN32 API. It also adds other stuff like a Document/View architecture, object persistence and collections that have no direct counterpart in WIN32.The C++ standard library does provide such things though.
Dave McLelland at 2007-11-11 2:09:29 >
# 2 Re: WIN32 and MFC Relationship
Hi,MFC is a wrapper, and in some cases an extension, of the Win32 API.
There are things in Win32 that you can't find in MFC and vice-versa...
While I know people still afraid to touch MFC and would rather spend lots of time creating stuff in Win32, most people will use MFC to do anything it can and use the Win32 to code stuff MFC can't do.
I personally put MFC to work to save me time and effort so I don't lose time on a project and its interface is just easier (in most cases) to use...
MFC was avoided by many due to its size. Years and years ago, it cost a fortune for a megabyte of harddisk space and it was hard to tell a customer that they needed a megabyte Dll to run your program...so MFC took a little while to catch on.
But now since you can get 200 Gigs for a couple hundred bucks, MFC is widly used except by a few die hard Win32Api programmers who refuse to use MFC out of fear or pride...
So to sum up...a good programmer will use whatever he\she can to get the job done quickly, effectivly and with as few bugs as possible. So you will find that both are used all the time to acomplish whatever needs to get done.
oktronic at 2007-11-11 2:10:26 >
