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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham 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 09:13:38 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!news.teledanmark.no!news01.chello.no!uio.no!ntnu.no!not-for-mail From: Preben Randhol Newsgroups: comp.lang.ada Subject: Re: MFC Date: Thu, 20 Mar 2003 17:13:37 +0000 (UTC) Organization: Norwegian university of science and technology Message-ID: References: <1048176444.65357@master.nyc.kbcfp.com> NNTP-Posting-Host: kiuk0152.chembio.ntnu.no X-Trace: tyfon.itea.ntnu.no 1048180417 14410 129.241.83.78 (20 Mar 2003 17:13:37 GMT) X-Complaints-To: usenet@itea.ntnu.no NNTP-Posting-Date: Thu, 20 Mar 2003 17:13:37 +0000 (UTC) User-Agent: slrn/0.9.7.4 (Linux) X-Received-Date: Thu, 20 Mar 2003 18:13:37 MET (news01.chello.no) Xref: archiver1.google.com comp.lang.ada:35572 Date: 2003-03-20T17:13:37+00:00 List-Id: Hyman Rosen wrote: > Dmitry A. Kazakov wrote: >> 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? (:-)) > > We've written largish C++ applications with MFC and they don't leak. > Did you acquire any evidence that the leak was due to internal MFC > behavior rather than your own failure to manage resources correctly? > comp.lang.c++