Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail
From: "U.Mutlu" <for-usenet@mutluit.com>
Newsgroups: comp.lang.c++
Subject: Re: What would happen if your destructors aren't get called?
Date: Sat, 04 Feb 2012 00:23:41 +0100
Organization: mutluit.com
Lines: 14
Message-ID: <4F2C6C7D.4020500@mutluit.com>
References: <jghp01$ak1$1@speranza.aioe.org> <9p37i4Fjr2U1@mid.individual.net>
NNTP-Posting-Host: 1sJgbIXBNgWfdeX/Oe8qvA.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0.1) Gecko/20111121 Firefox/8.0.1 SeaMonkey/2.5
X-Notice: Filtered by postfilter v. 0.8.2
Disposition-Notification-To: "U.Mutlu" <for-usenet@mutluit.com>
Xref: x330-a1.tempe.blueboxinc.net comp.lang.c++:13730

Ian Collins wrote, On 02/04/12 00:05:
> On 02/ 4/12 12:01 PM, U.Mutlu wrote:
>
>> How can Microsoft sell such a buggy product and call it "C++ compiler"?
>
> Show me a bug free compiler and I'll show you a flying pig.

But if such elemantary parts like automatically called destructors
aren't working in a C++ compiler, then it can't be a C++ compiler.

Imagine what happens if that product is used in sensitive areas
like the NASA, airplane industry, defense companies etc. etc...

A C++ conformance body should control the vendors.