Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <01af01c23dab$0e4e0010$a352a518@samsystem> From: "Samuel" To: References: <79218202D4B9D4118A290002A508E13B79C391 AT PNZEXCHANGE> Subject: Re: new vs malloc, was BUG - Cygwin to GNU CC compatibility Date: Tue, 6 Aug 2002 17:40:40 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 ----- Original Message ----- From: "Ross Smith" To: "'Chan Kar Heng'" ; Sent: Tuesday, August 06, 2002 1:49 PM Subject: RE: new vs malloc, was BUG - Cygwin to GNU CC compatibility > > No user code should ever use "delete"; it should only appear in the > implementation of a container or smart pointer. What? I must misunderstand what is meant, since user code must always use "delete" for each "new", unless the documentation of a function clearly states that it is the function's responsibility to "delete". -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/