Thread Synchronization :: Win32 API vs. MFC

Hi.

I design and implement Windows programs using MFC and its doc/view architecture. Currently I am studying Jeffrey Richter's Programming Applications for Microsoft Windows. It is an amazing booking with unparrelled insights to Windows core.

In his book, Richter demonstrates thread synchronization both at user-mode and at kernel object levels using Win32 API. For example, for critical sections, you can call EnterCriticalSection(...). For events, you can call CreateEvent(...).

Anyways, I have studies from Jeff Prosise's Programming Windows with MFC. Prosise demonstrates thread synchronization using MFC tools including CCriticalSection, CEvent, CMutex, as well as CSingleLock.

Again, I have no experience with Win32 API GUI tools. I would like to know is it what is the preferred tool for thread synchronization: Win32 API or MFC? Both techniques make use of the same thread synchronization tools. I want to know which technique is more powerful now and in the future.

I really enjoy working with Win32 API, just not for GUI.

Thanks,
Kuphryn

As you have already mentioned, the MFC variants are simply wrappers around the same API routines, so essentially they are the same. If you are in any case working with MFC, use the MFC versions, if not, use the API calls directly. I do not believe there is a preffered way - it depends on the rest of the project/project team.

I always use the API directly, for the GUI as well.

Thanks.

I prefer Win32 API for everything except GUI. I still int the process of incorporating the Win32 API thread synchronization functions in my programs.

Kuphryn