What is the differance between win32 API and MFG?
What is the differance between win32 API and MFG?
what is mfg??
zMan
You probably thinking about Mfc
Api means Aplication programing interface and that is the native way your application can comunicate with windows. Anything you want to do that involve windows is done through the api.
Mfc means Microsoft foundation class and is basicly a wrapper class for the Api.If you use Mfc you interact with the Api in a object oriented way. Mfc is alot easier and faster way to write applications but you don't have the same speed and power as you do with with Api.
you forgot to mention... you will also keep more of your hair with the MFC then with the API....
zMan
LOL...contriversal!!Originally posted by zMan
you forgot to mention... you will also keep more of your hair with the MFC then with the API....
We havent had this months MFC Vs API argument thread have we?
So, it would be in my best intrest to learn api before I take visual c++ next fall which I'm fairly sure uses mfc?
Yup...got it in 1Originally posted by Intimd8r
So, it would be in my best intrest to learn api before I take visual c++ next fall which I'm fairly sure uses mfc?
MFC is cool and a real powerful tool, but without a founding knowledge of API it can be a bit limp
MMmm Mfc is better then Api...There we go ..a well founded argument with lots of fact.Originally posted by Fordy
We havent had this months MFC Vs API argument thread have we?
Doh...there goes the neighbourhoodOriginally posted by Barjor
MMmm Mfc is better then Api...There we go ..a well founded argument with lots of fact.
>MMmm Mfc is better then Api...There we go ..a well founded argument with lots of fact.
No way. You're wrong. Proof here.
-Govtcheez
[email protected]
mm I guess I was wrong..If it's on the internet I guess it has to be true.
MFC uses api so how can one be better than the other. I personally prefer to use MFC because of the reduction in time. Even if I did not use the MFC I would create my own classes to wrap the API. I do not like the copy-and-paste approach to developing applications. Hey if something works make it generic work out the logic bugs, test it, and forget about the details.
Eventually I will move on to building bigger and better applications out of the smaller tools that I have built.
I must agree that knowing the api is, if not necessary, at least extremely helpful when developing with the MFC. But why would anyone want to reinvent the wheel? Chances are that by the time anyone just starting out becomes fully proficient with using only the API the .NET framework will be have fully matured if not expired and the API will seem like assembly language (I think that it does already).
inZane
--true programmer's don't comment--
--programmer wannabes complain about it--
true programmers dont comment wtf??!?!?! I wrote something and came back to it and had to use my own comments to figure out what the hell i had written. Guess you really are a bit zaney.
Time to write an app with a main maximised window, toolbar (no buttons activated), menu, config file, sockets, app update system and a generic frame buffering painting.
MFC 1hour with the wizard and my libraries.
WIN32 1 day with my libraries.
But I prefer the API as most of my controls are customised and ownerdrawn. I find it more flexible.
"Man alone suffers so excruciatingly in the world that he was compelled to invent laughter."
Friedrich Nietzsche
"I spent a lot of my money on booze, birds and fast cars......the rest I squandered."
George Best
"If you are going through hell....keep going."
Winston Churchill
OK well maybe a few comments here and there...
but if you have a descent style and and provide meaningful names anyone should be able to follow your code....
Yes comments nowadays are mainly for bad code....
zMan