The WNDCLASSEX...

I attempted to make a Windows program using raw API before but I didnt get very far... I like to completely understand everything until I move on... I dont like grey areas...

After all this talk about how much you guys dont like MFC, has inspired me to give it another try... Although I will probably have lots of questions... if you dont mind answering them...

My first is about the WNDCLASSEX struct... and its cbClsExtra member....

It says in MSDN that it specifies the number of extra bytes to allocate following the window-class structure.

My question is why would you want to or need to do this?

Try this web page:

www.winprog.org

Alright thanx... I will start there...

just one question _stdcall... what exactly does this do? What is the difference between a function without it... and one that has this included...

_stdcall just tells the compiler whether the called function or
the calling function cleans up the stack. I
believe that __stdcall says that the called function cleans up the stack when it is about to return. So if it is called in a bunch of different places, all of those calls do not need to extra code to clean up the stack after the function call.

Is there a reason why you need __stdcall? I do not believe that all compilers support __stdcall.


----------------------------------------------------------------------------------

Quote:

---

and one that has this included...

---

I did not understand that... what to you mean by that

i just meant... what is the difference between a function with __stdcall and one without it...

but you pretty much answered it...

I am not using... really... but for int WINAPI WinMain(...)

I found something on the site you mentioned that it was defined as __stdcall... and I was curious what it was... I have seen it before... but never really cared to much about what it was...

So I am not using it explicitly... WinMain() is

on wait... just another question...

Why would it matter which function cleans up the stack (called/calling) ?