Why do MS prefer to provide a new function, Cwnd::CreateEx rather than override

Why do MS prefer to provide a new function, CWnd::CreateEx
rather than override CWnd::Create?

backward compatibility?

Because there are 2 WinAPI Functions CreateWindow and CreateWindowEx, of course windows is C written so there is no way for override ... I think CreateWindow is just a macro calling CreateWindowEx by providing a default parameter ...

Yeah, but I think it's not because it's C written (C++ is C written, too :rolleyes: ), rather WinAPI is designed not only for C++, but also for C, VB... those don't have function overriding

Quote:

---

Originally Posted by sephiroth2m

Yeah, but I think it's not because it's C written (C++ is C written, too :rolleyes: ), rather WinAPI is designed not only for C++, but also for C, VB... those don't have function overriding

---

I meant that the WinAPI is purely C written (98% I think, just take a look at the ReactOS Source Code), VB was invented later, and just supports the C Calling Convention __stdcall ...