From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00, XPRIO_SHORT_SUBJ autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,a3b67c7e4c7509ad X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-03-20 06:40:59 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!nntp.cs.ubc.ca!nntp-relay.ihug.net!ihug.co.nz!west.cox.net!cox.net!cyclone1.gnilink.net!spamkiller2.gnilink.net!nwrdny02.gnilink.net.POSTED!53ab2750!not-for-mail From: "Frank J. Lhota" Newsgroups: comp.lang.ada References: Subject: Re: MFC X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-ID: <_pkea.75445$gi1.73160@nwrdny02.gnilink.net> Date: Thu, 20 Mar 2003 14:40:58 GMT NNTP-Posting-Host: 141.157.181.168 X-Complaints-To: abuse@verizon.net X-Trace: nwrdny02.gnilink.net 1048171258 141.157.181.168 (Thu, 20 Mar 2003 09:40:58 EST) NNTP-Posting-Date: Thu, 20 Mar 2003 09:40:58 EST Xref: archiver1.google.com comp.lang.ada:35566 Date: 2003-03-20T14:40:58+00:00 List-Id: "Dmitry A. Kazakov" wrote in message news:usvi7vkqagf0bmo6eosemtvolqb6h497oe@4ax.com... > The only problem we faced, before abadoning any use of MFC in our C++ > projects, was that it leaked in many places on many occasions. Is that > horrible enough? (:-)) Amen! For reasons I still don't understand, MFC has its own memory management scheme, and you are forced to play by their own set of rules for handling memory to avoid dire consequences. My experience indicates that if you are going to use MFC at all, use it for everything in the project, including threads, sockets, etc. Conversely, if you wish to avoid using MFC in some areas, skip MFC all together -- an option that more and more programmers are endorsing.