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,FREEMAIL_FROM
	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 08:07:25 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!bigboote.WPI.EDU!news.tufts.edu!uunet!dca.uu.net!ash.uu.net!spool0902.news.uu.net!not-for-mail
Date: Thu, 20 Mar 2003 11:07:23 -0500
From: Hyman Rosen <hyrosen@mail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.4a) Gecko/20030313
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: MFC
References: <b5apqq$pl5$4@atlantis.news.tpi.pl>
 <usvi7vkqagf0bmo6eosemtvolqb6h497oe@4ax.com>
In-Reply-To: <usvi7vkqagf0bmo6eosemtvolqb6h497oe@4ax.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Organization: KBC Financial Products
Message-ID: <1048176444.65357@master.nyc.kbcfp.com>
Cache-Post-Path: master.nyc.kbcfp.com!unknown@nightcrawler.nyc.kbcfp.com
X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/)
NNTP-Posting-Host: 204.253.250.10
X-Trace: 1048176444  27793 204.253.250.10
Xref: archiver1.google.com comp.lang.ada:35571
Date: 2003-03-20T11:07:23-05:00
List-Id: <comp.lang.ada>

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?