delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2002/08/06/20:40:31

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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" <samuel AT socal DOT rr DOT com>
To: <cygwin AT cygwin DOT com>
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
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

----- Original Message -----
From: "Ross Smith" <rosss AT pharos DOT co DOT nz>
To: "'Chan Kar Heng'" <karheng AT softhome DOT net>; <cygwin AT cygwin DOT com>
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019