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,6009c73a58f787a0 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-01-15 08:31:36 PST Path: archiver1.google.com!news2.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news-feeds.jump.net!uunet!dfw.uu.net!ash.uu.net!spool0901.news.uu.net!spool0900.news.uu.net!reader0900.news.uu.net!not-for-mail Message-ID: <3C44565F.9030403@mail.com> Date: Tue, 15 Jan 2002 11:18:39 -0500 From: Hyman Rosen User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.7+) Gecko/20010929 X-Accept-Language: en-us MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: How to avoid unreferenced objects (mutexes etc) References: <3c3ee8c8.105408250@News.CIS.DFN.DE> <3c429d1c.2624281@News.CIS.DFN.DE> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Organization: KBC Financial Products Cache-Post-Path: master.nyc.kbcfp.com!unknown@mosquito.nyc.kbcfp.com X-Cache: nntpcache 2.3.3 (see http://www.nntpcache.org/) NNTP-Posting-Host: 204.253.250.10 X-Trace: 1011111441 reader0.ash.ops.us.uu.net 4865 204.253.250.10 Xref: archiver1.google.com comp.lang.ada:18937 Date: 2002-01-15T11:18:39-05:00 List-Id: Matthew Heaney wrote: > The problem is that the language doesn't have a termination handler for > blocks, a la a "finally" clause in Java or Win32 Structured Exception > Handling. So you have to create "unused" objects as a work-around. In C++, this is considered a desirable design paradigm, not a problem. If you happen to be controlling several resources, the "finally" way marches off the right side of the page - try { // acquire resorce 1 try { // acquire resource 2 try { // acquire resource 3 // now do something } finally { // release resource 3 } } finally { // release resource 2 } } finally { // release resource 1 } As opposed to Res1Holder r1; // acquire resource 1 Res2Holder r2; // acquire resource 2 Res3Holder r3; // acquire resource 3 // do something