220 7587 article Path: news.gmane.org!not-for-mail From: Olaf van der Spek Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Fixing the private method issue Date: Mon, 4 Nov 2013 15:14:56 +0100 Lines: 24 Approved: news@gmane.org Message-ID: References: <8d5f90be-ed45-4b42-9ddd-d6e2497c8166@isocpp.org> <997f6a58-e8ff-4656-b7be-7714dd2a7240@isocpp.org> <1CD4DBEC-8081-42AD-861A-FF87D7E55606@gmail.com> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: ger.gmane.org 1383574563 31834 80.91.229.3 (4 Nov 2013 14:16:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 4 Nov 2013 14:16:03 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBC5NB45SSABBBYOX32JQKGQE24JSK4A@isocpp.org Mon Nov 04 15:16:08 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-wg0-f70.google.com ([74.125.82.70]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VdKvi-00028V-Kv for gclcip-std-proposals@m.gmane.org; Mon, 04 Nov 2013 15:14:58 +0100 Original-Received: by mail-wg0-f70.google.com with SMTP id c11sf3456980wgh.9 for ; Mon, 04 Nov 2013 06:14:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:list-subscribe :list-unsubscribe:content-type; bh=FdnO3edmFqzSRIKRscCsH67BiV1sr7+Qq96jASgQQhM=; b=MtOvz/csrLtgRcbw4yCdDeXROTNwkj/a5FIIH7f50Bii/IjwuMaoxWH3Q//8dMlxhD rrBTJlsWC/9/WDPVF3eyRIvHrU9meW3ZejTcS+jA0I6fi3woDtmZoubJooaL+Z68J1bn oQKX3aSCRajk8F0HLqpApvS3QD4mptfWxCdTmWdm2iv/No9V4npAQ8um2rLv5qTpwMPs /IAG381552Ldi2CouqkaTmcgch+24fYrSi9/UUWAS41p01B9H1Pm4TOZj5HacIw49YqY b7+MLtCUsJY4K+GApCrEFwORBf8KvEV/zVT5N8soXu3ecSGHDOmpZdw/1MiwcaQArzXv jIWw== X-Gm-Message-State: ALoCoQnF5AGFTf8S5j/WCu9qyYNETOOX7YsPzeV0Jc2ghU84TFLmOMf3ID6lZ3Njn/25B7enw3Os X-Received: by 10.205.24.131 with SMTP id re3mr3019940bkb.0.1383574498172; Mon, 04 Nov 2013 06:14:58 -0800 (PST) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.180.72.206 with SMTP id f14ls482846wiv.47.canary; Mon, 04 Nov 2013 06:14:57 -0800 (PST) X-Received: by 10.204.96.203 with SMTP id i11mr17785bkn.56.1383574497146; Mon, 04 Nov 2013 06:14:57 -0800 (PST) Original-Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [2a00:1450:4010:c04::233]) by mx.google.com with ESMTPS id ns6si2791403bkb.336.2013.11.04.06.14.57 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Nov 2013 06:14:57 -0800 (PST) Received-SPF: pass (google.com: domain of olafvdspek@gmail.com designates 2a00:1450:4010:c04::233 as permitted sender) client-ip=2a00:1450:4010:c04::233; Original-Received: by mail-lb0-f179.google.com with SMTP id w6so5405708lbh.38 for ; Mon, 04 Nov 2013 06:14:56 -0800 (PST) X-Received: by 10.112.168.170 with SMTP id zx10mr11390711lbb.0.1383574496629; Mon, 04 Nov 2013 06:14:56 -0800 (PST) Original-Received: by 10.152.5.229 with HTTP; Mon, 4 Nov 2013 06:14:56 -0800 (PST) In-Reply-To: <1CD4DBEC-8081-42AD-861A-FF87D7E55606@gmail.com> X-Original-Sender: olafvdspek@gmail.com X-Original-Authentication-Results: mx.google.com; spf=pass (google.com: domain of olafvdspek@gmail.com designates 2a00:1450:4010:c04::233 as permitted sender) smtp.mail=olafvdspek@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: 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:7587 Archived-At: On Mon, Nov 4, 2013 at 3:01 PM, Marshall Clow wrote: > Not entirely true. In general, callers don't need to know the layout. The > layout is (only?) required when accessing data members, the size is only > required when creating an object on the stack. > > > Counterexample: > struct Foo; > Foo * f = new Foo; > > This calls operator new ( size_t ) to allocate memory. > How much memory should be allocated? One could use a factory function Or some (automatic) get_size() function could be generated -- --- 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/. .