220 19657 article Path: news.gmane.org!not-for-mail From: Myriachan Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Templated malloc, calloc and realloc - remove all the 'new's! Date: Tue, 4 Aug 2015 14:18:23 -0700 (PDT) Lines: 63 Approved: news@gmane.org Message-ID: References: <7fc7f182-f8ad-496e-947a-e8f253ac4676@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_3623_342577963.1438723104099" X-Trace: ger.gmane.org 1438723107 9264 80.91.229.3 (4 Aug 2015 21:18:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 4 Aug 2015 21:18:27 +0000 (UTC) To: ISO C++ Standard - Future Proposals Original-X-From: std-proposals+bncBDKLT4PURQHRBIOYQSXAKGQEBPTAXQA@isocpp.org Tue Aug 04 23:18:27 2015 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-oi0-f69.google.com ([209.85.218.69]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZMjbP-0006IS-6N for gclcip-std-proposals@m.gmane.org; Tue, 04 Aug 2015 23:18:27 +0200 Original-Received: by oiho132 with SMTP id o132sf30706524oih.1 for ; Tue, 04 Aug 2015 14:18:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :content-type:x-original-sender:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=baSyYRE4lxQLr+31YSCuSC5vGFNfQUl88Tax8CoQQyM=; b=m8brgLoXKfKGBOszwba3sQujnLnufMNNNWCTnglX6ilkeukPrp+He+mwzn+f+qSUyR YTA098TUGdoYVfmVPRXDM1OM1tj6zwPVAY2a+YzhH7LecQn3Jk4PNhdNbwyypQLgf6P8 mGeDj9q1PO85Y9bXfX57YHHyrNSKvfyu8FxeSdSH727TDvv3uDfJF/pAPBhG8zKcomMT y2YJWnXlvR7eFupTPyYmpBYs2uaB1UCWU+SGRCfAm9FCr6242klNoK6RMqKrhvMygoEL m1YX1Ax8yx5G4ZPdvY3u28AXk6d0gX5c7Tx4yz8CvourXQLQWnZDmEfXRp2jeGp7JD/9 1FYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version:content-type:x-original-sender:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=baSyYRE4lxQLr+31YSCuSC5vGFNfQUl88Tax8CoQQyM=; b=kPiWvawOi3v+0ROcBw/KY6EtVD4mAPC+Iiu+FLMW5rsMWGnQcondPxMbll5UN40nwi rB3o/PJyVjt0mf5+BnPIP46R+MuGtwDYEcm+O8HT5/IKlRfiBmUZwBG8zFMknoS83NzO pb5DjgjuT3U/3At2c7h298B3VpI4mb9H5MHdEfuo+vZDnOJDO0ShfYxu6GluT0La+yCN hJW7mm9yWingh9DLS0RTsIBDfC4LjG4/kcr3NfBBuIdeUig2fPFsXVfqn7ZjFTCviT8z pIKRG4qqqBzD5jhNVvoMKUoqeh2jdBZIEiax7JRIplyteuwtNpxDSAVLIA4ocsfkqYNT 1Bhw== X-Gm-Message-State: ALoCoQmRmJ1yOBhCiTsAk44IEhUhNoODGj5bZ5pqvpLPI8OPjiDEjBHJPV1NqgyTafRi5a6XIJXc X-Received: by 10.107.162.148 with SMTP id l142mr5142140ioe.22.1438723106005; Tue, 04 Aug 2015 14:18:26 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.107.31.210 with SMTP id f201ls390761iof.72.gmail; Tue, 04 Aug 2015 14:18:25 -0700 (PDT) X-Received: by 10.50.142.39 with SMTP id rt7mr361800igb.17.1438723105350; Tue, 04 Aug 2015 14:18:25 -0700 (PDT) In-Reply-To: X-Original-Sender: myriachan@gmail.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: X-Spam-Checked-In-Group: std-proposals@isocpp.org X-Google-Group-Id: 399137483710 List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:19657 Archived-At: ------=_Part_3623_342577963.1438723104099 Content-Type: multipart/alternative; boundary="----=_Part_3624_1200402199.1438723104099" ------=_Part_3624_1200402199.1438723104099 Content-Type: text/plain; charset=UTF-8 On Sunday, August 2, 2015 at 3:21:28 PM UTC-7, Ville Voutilainen wrote: > > Placement forms and class-specific overloads continue to be useful, and > we're > very likely to continue improving new, like making it alignment-aware. > This is where my admittedly-radical suggestion earlier came from: it explicitly defines what happens when you do new/delete/new[]/delete[]. It would permit overriding compiler-default behavior, like where to store the array length. It also defines issues such as alignment. Melissa -- --- You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group. To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org. To post to this group, send email to std-proposals@isocpp.org. Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/. ------=_Part_3624_1200402199.1438723104099 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Sunday, August 2, 2015 at 3:21:28 PM UTC-7, Ville Vouti= lainen wrote:
Placement forms a= nd class-specific overloads continue to be useful, and we're
very likely to continue improving new, like making it alignment-aware.

This is where my admittedly-radical suggestion ea= rlier came from: it explicitly defines what happens when you do new/delete/= new[]/delete[].=C2=A0 It would permit overriding compiler-default behavior,= like where to store the array length.=C2=A0 It also defines issues such as= alignment.

Melissa

--

---
You received this message because you are subscribed to the Google Groups &= quot;ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposa= ls+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/<= /a>.
------=_Part_3624_1200402199.1438723104099-- ------=_Part_3623_342577963.1438723104099-- .