EWin vs. MFC

It is natural and logical to compare EWin to MFC, Microsoft's Foundation Classes. Both libraries have their pros and cons, but I think that for many projects, EWin wins out. EWin is designed with reliability and code-cleanliness as its main goals, whereas MFC has been carefully engineered to be wizard-able, that is, MFC code can be automatically generated by dialogs in the Microsoft Visual Studio environment. Using Wizards to write your code is slightly faster than writing it by hand, but the resulting code is much harder to understand.

Also, MFC is not ANSI compliant. The most obvious problem is for-loop scope -- MFC uses the old for-loop scoping rules. Microsoft added a special mode to their compiler just for MFC ... certain rules are turned off and other rules are treated differently. Other compiler vendors are forced to follow suit and modify their compilers to support MFC.

EWin tries to be as ANSI-compliant as possible in a Win32 environment (which is to say, not very -- certain keywords such as export and import are pretty much necessary to use DLLs and other Win32 features). But I am confident that I can easily port EWin (within a day or so) to any existing Win32 C++ compiler.

I will provide more MFC vs. EWin details soon...