Drawbacks using MFC
-
Are there any negative affects with MCF? Does my program runs slower, do they take more memory, do they crash more often? Then if I code straight win32? I have to write a program that is stable, so are ther any drawbacks by using MCF instead of win32? TIA Fredrik Sigbjörn SigSoft
-
Are there any negative affects with MCF? Does my program runs slower, do they take more memory, do they crash more often? Then if I code straight win32? I have to write a program that is stable, so are ther any drawbacks by using MCF instead of win32? TIA Fredrik Sigbjörn SigSoft
I thought the idea of MFC was that it was a SMART Library of code and that the only problem comes when you add your bit :-) ?? I see the problem with MFC being that you never learn the Windows API?? Jay :-D http://home.clara.net/jaylazz
-
Are there any negative affects with MCF? Does my program runs slower, do they take more memory, do they crash more often? Then if I code straight win32? I have to write a program that is stable, so are ther any drawbacks by using MCF instead of win32? TIA Fredrik Sigbjörn SigSoft
MFC is a great time-saver, and as long as yu don't step too far out of MFC's own (sometimes quirky) sense of reality, you should be fine. Any program that makes use of a pre-designed class framework is going to be larger than one which doesn't. MFC programs will grow if you include any of the following capabilities: - support for windows sockets - support for MFC collection classes - support for com/atl/activex - support for databases (odbc, ado, dao) Of course, you can compile your app using the MFC DLLs which makes your programs smaller at the expense of having to ship the MFC DLLs, as well as the possiblity that some rogue install program will overwrite those DLL's with an older version. I personally prefer to statically link MFC. Sure, it makes my apps a little larger, but I don't have to worry about those stupid DLLs either.