220 4691 article Path: news.gmane.org!not-for-mail From: Lawrence Crowl Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Remove vector? Date: Tue, 28 May 2013 15:43:53 -0700 Lines: 48 Approved: news@gmane.org Message-ID: References:

<7371f4b8-8c47-4f17-af1e-902a5c8b17e4@isocpp.org>

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 1369781037 4302 80.91.229.3 (28 May 2013 22:43:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 28 May 2013 22:43:57 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCY3D77DYUDBBK7GSSGQKGQE56AU4HQ@isocpp.org Wed May 29 00:43:57 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-qa0-f72.google.com ([209.85.216.72]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UhScW-0005Pk-Ky for gclcip-std-proposals@m.gmane.org; Wed, 29 May 2013 00:43:56 +0200 Original-Received: by mail-qa0-f72.google.com with SMTP id bs12sf4555123qab.11 for ; Tue, 28 May 2013 15:43:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlers.com; s=googlers; h=x-beenthere: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:x-google-group-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe :content-type; bh=3duHvREn6Ut13SNhfqtQspSGcapLekOxsKov8NZK3aA=; b=GpGtfRRLV+6tnVtWcyLmq1UGKt0Ixemrr4IEim8h1O23dVmHiRxziWfDALRHu625WG /AhKd3uGpddmCAQQhBDn6hyYZX1DXTVh/9sNjzV3+eeBWNqA2tmSwTWDZntOptyZ2R78 DpqjwF4hiReB95dDdEVsGk+/NqIV6l6DzVnZE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-beenthere:mime-version:in-reply-to:references:date:message-id :subject:from:to:x-gm-message-state:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe:content-type; bh=3duHvREn6Ut13SNhfqtQspSGcapLekOxsKov8NZK3aA=; b=IbpiQQlaZtv2dDordqqUGbTUQMS2PjRAPGDp8fgCtX7Pkf+ccLWVOlUxjJ5pYBzcsq MY1E9KmAuxe0GVE7++AkfmyF5jJ3V6EvO1UIPmHIJmHdrei+18SOMDDYYfaM6V3Nz3D/ CxvteKVgCKMx4qt+mIcvnnjfm1qmjDmmeQxAMIP23n2Lry8AB3TAF2rj1CcWQFqz5Ogg 7vgdVkQWwYhMh9rt/UPCyy8uDH64ebO1tc1cgn0zAtDe9n7IPKaGNAmrIDsgbZOAZ/Ge JBOp7PQJQmh5Yad+q5UQaLH+0btyiy2fuOhpAr7skiqN7hgLBV36a+voGgVlQoV8Nyhl /oJg== X-Received: by 10.236.118.196 with SMTP id l44mr16479815yhh.48.1369781035724; Tue, 28 May 2013 15:43:55 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.49.15.66 with SMTP id v2ls3726996qec.98.gmail; Tue, 28 May 2013 15:43:54 -0700 (PDT) X-Received: by 10.229.149.198 with SMTP id u6mr9626qcv.20.1369781034673; Tue, 28 May 2013 15:43:54 -0700 (PDT) Original-Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [2607:f8b0:400d:c00::234]) by mx.google.com with ESMTPS id k1si27857647qaz.107.2013.05.28.15.43.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 15:43:53 -0700 (PDT) Received-SPF: pass (google.com: domain of crowl@google.com designates 2607:f8b0:400d:c00::234 as permitted sender) client-ip=2607:f8b0:400d:c00::234; Original-Received: by mail-qa0-f52.google.com with SMTP id bv4so1824495qab.4 for ; Tue, 28 May 2013 15:43:53 -0700 (PDT) X-Received: by 10.49.95.231 with SMTP id dn7mr39193739qeb.63.1369781033422; Tue, 28 May 2013 15:43:53 -0700 (PDT) Original-Received: by 10.229.150.207 with HTTP; Tue, 28 May 2013 15:43:53 -0700 (PDT) In-Reply-To: X-Gm-Message-State: ALoCoQmZY2hYnKaX/Ddh1AjPIDjWyGtmCLv40/4TTRxoPncf7cEfelH7wavHbtCwIHCV5t196PbSIilx1MqQtc2XLS5tpTrJZszYzAe5EczrwpifWhgYAUnC1j5AsAWJ9HyYoy2EKKaGdTZyjNFZOJkpq4g0lCH1iBCacxLqLbWmFMiFmm0v5r6rEDQsfPMjXm+h8bcRs0+m X-Original-Sender: crowl@googlers.com X-Original-Authentication-Results: mx.google.com; spf=pass (google.com: domain of crowl@google.com designates 2607:f8b0:400d:c00::234 as permitted sender) smtp.mail=crowl@google.com; dkim=pass header.i=@googlers.com; dmarc=pass (p=QUARANTINE dis=none) d=googlers.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:4691 Archived-At: On Tuesday, May 28, 2013 1:28:06 PM UTC-7, Zhihao Yuan wrote: > I like the idea of providing a replacement, but I don't think a > 'drop-in replacement' is a requirement. `vector` still > works, and users can rewrite their code if they want. It is sometimes difficult to rewrite code. First, the code base may be very large. Source code bases in excess of 20 million lines are common. Expect much code bases to exist. Second, sometimes that code is part of binary libraries. To get a change you need to go back to the library vendor, request the change, hope they have time to deal with your legacy platform, and you get the idea. Third, the author of the code may be long gone. So, a rewrite would require a programmer to understand the subtleties of that particular use, which takes time. Now multiply by the code base size. On 5/28/13, Nicol Bolas wrote: > When breaking people's code, it is generally advisable to minimize > the disruption. And it'd be a lot easier to get through the > committee if you can show them that the breaking changes will be > noisy *and* that the changes can be easily repaired. > > A drop-in replacement would cover the latter. Agreed. A breaking change should have a migration plan. For C++11, I argued that we could drop support for the old use of the auto keyword because we had a simple migration plan. = Remove all uses of the auto keyword in the code base. = You now have a program that is both C++98 and C++11 conformant. = Add the new use of auto when desired. It certainly helped the argument that two thirds of the uses of auto I found on code.google.com were in compiler conformance test suites. -- Lawrence Crowl -- --- 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/?hl=en. .