Platform SDK vs. MFC

[DarkTwilkitri]

Hey, I've been thinking about learning C/C++. I would have assumed that MFC would be the way to go when making windows programs, since it's the later of the choices... however, I've read books (well, a book) which say it's better to use the Platform SDK.
Furthermore, after looking at simple code for them, MFC scares me There wasn't even a main() or WinMain(), and it ran... that just seems wrong, somehow...

[ender]

If you want to learn C++, I suggest learning the langauge before jumping into any 'SDK'. Learn the basics. After that, the other stuff will come in naturally. There is nothing wrong with writing console based applications before jumping into windows programming, which is tough. Nothing beats a good base knowledge.

Furthermore, MFC 'could' be considered a SDK for windows. So, unless the SDK for this uses the win32api, I don't know what alternative M$ has out there, besides win32api and .NET.

My advise, go learn the basics, then go to windows programming.

Sorry if this is too long winded.

-Ted

[DarkTwilkitri]

By the Platform SDK I mean, for example to create a window first you fill in a window class structure, then RegisterClass it, then CreateWindow it, etc... which are all the functions in what the help calls the Platform SDK, as differentiated from MFC, where you derive classes from the base classes and then get them working through means which aren't apparent to me.

Thanks for your concern, but I already know that I have to learn the language fairly well before I should start doing windowed stuff . I was just wondering... I was actually advised by someone else that I shouldn't learn either of them, and I should wait until Longhorn comes out because it'll probably have a different API :/.

I know generic programming, in that I know how control structures et al work, from Java and Casio9850GB+, so mostly I need to learn the things which C/C++ have which they don't, such as pointers et al.

Heh... I'm not sure how you can call that long-winded.

[Valmont]

MFC is nothing else than "(class) wrappers" for the win32api (win32 SDK).
This way using the most used win32api methods is easier and faster.

Secondly MFC uses a "Document/View" structure. This is called a framework. Before learning any framework one needs a decent understanding of c++ and OO.

MFC doesn't have a "int main()" indeed.
This is related to the framework (document/view architecture).
I.e. you need a Document to storre varaibles in it. You need a View to make things visible, etc.

Forget MFC I keep saying that. First C++ and OO. Then the serious work.