last time I developed a GUI application for windows (in 1998), I was using C++ and Win32. We tried MFC and it just did not do it. I remember sick solutions for sick problems in MFC, like sending messages to be called back again later. I simply wrote some C++ wrappers for win32 calls. And I joined these wrappers into base class and member class relationships. The resulting code was very clear, short and maintainable. It contained an activex control container (written in C++) -- not using ATL. I'm amazed that there are still C++ programmers, which don't know about how to wrap a fallible Win32 resource into a C++ class and how to chain such classes into base and member class relationships. I'm amazed that there still seem to be C++ programmers, which don't know how to abort the construction of an object. -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Robert Ramey Sent: Thursday, April 09, 2009 12:17 To: boost-users@lists.boost.org Subject: Re: [Boost-users] Boost thread conflicts with MFC aaaaa .... what do you use instead for development of a C++ windows GUI program? Robert Ramey peter_foelsche@agilent.com wrote:
It amazes me, that there are still people working with MFC. It does not make much sense to use MFC, after C++ Exception Handling was introduced in 1995. After C++ Exception Handling was introduced one can use constructors to allocate fallible resources.
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users