Eventually, Borland discontinued OWL development and licensed the distribution of the MFC headers, libraries and DLLs from Microsoft for a short time, though it never offered fully integrated support for MFC. The Object Windows Library (OWL), designed for use with Borland's Turbo C++ compiler, was a competing product introduced by Borland around the same time. MFC is not included in the free edition of Visual C++ 2005/2008/2010 Express. MFC 9.0 was released with Visual Studio 2008. MFC 8.0 was released with Visual Studio 2005. The name Microsoft Foundation Classes (MFC) was adopted too late in the release cycle to change these references. ![]() During early development what became MFC was called "Application Framework Extensions" and abbreviated "Afx". One interesting quirk of MFC is the use of "Afx" as the prefix for many functions, macros and the standard precompiled header name "stdafx.h". Many of those functions share their names with corresponding API functions. Instead, programs create objects from Microsoft Foundation Class classes and call member functions belonging to those objects. In an MFC program, direct Windows API calls are rarely needed. C++ was just beginning to replace C for development of commercial application software at the time. MFC was introduced in 1992 with Microsoft's C/C++ 7.0 compiler for use with 16-bit versions of Windows as an extremely thin object-oriented C++ wrapper for the Windows API.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |