220 6696 <25ed07c5-174e-48d5-9326-bd199f365e85@isocpp.org> article Path: news.gmane.org!not-for-mail From: Bengt Gustafsson Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: A tool to check if breaking changes will actually break any code out there Date: Fri, 27 Sep 2013 18:03:57 -0700 (PDT) Lines: 84 Approved: news@gmane.org Message-ID: <25ed07c5-174e-48d5-9326-bd199f365e85@isocpp.org> References: Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_761_17449934.1380330238042" X-Trace: ger.gmane.org 1380330238 829 80.91.229.3 (28 Sep 2013 01:03:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 28 Sep 2013 01:03:58 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCRIRSPDTQIRBAGWTCJAKGQEVZWPX5A@isocpp.org Sat Sep 28 03:04:02 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-oa0-f71.google.com ([209.85.219.71]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VPix0-0006tI-6X for gclcip-std-proposals@m.gmane.org; Sat, 28 Sep 2013 03:04:02 +0200 Original-Received: by mail-oa0-f71.google.com with SMTP id f4sf10174422oah.10 for ; Fri, 27 Sep 2013 18:04:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe :content-type; bh=ADeWDoCY8D4hlOMdEFqDqX7b/8TRda5kp5CVUoBICJQ=; b=IUO2FsXy2K7VQLpXEo0k7tIkHjF8SMfxTwIH8e4NqDOGXqMPh6Fwm74ZU7X2iXTMEq NdPXCBS5GqKmOJefdNQGRCrryG5+UDZQ7nuuY6pVMkHviLP2/X7+vJMw45dHb1s3Y2Sd 2Tbd28kpkA/mSYLflb/r0IM9ZmIgtukadn8myI0LcHGy3qv97hf2dbqq6IKCKEsi/uWJ NJadHdyKMyIem5BdgITjVj3Z43Fq2woN0tZ4pl4FLhos3yRix4fumxm/B1HJYWPKD1a5 LUMBfI24PHeA+fQwDVDkJ3vYBQxs0okfRoJxRWWjznXzVWaBbdm53AAYg3V/ilUxTP0M mmrg== X-Received: by 10.43.114.67 with SMTP id ez3mr6168499icc.6.1380330241180; Fri, 27 Sep 2013 18:04:01 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.50.88.98 with SMTP id bf2ls655462igb.15.gmail; Fri, 27 Sep 2013 18:03:59 -0700 (PDT) X-Received: by 10.50.16.111 with SMTP id f15mr195337igd.2.1380330239727; Fri, 27 Sep 2013 18:03:59 -0700 (PDT) In-Reply-To: X-Original-Sender: bengt.gustafsson@beamways.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:6696 Archived-At: ------=_Part_761_17449934.1380330238042 Content-Type: text/plain; charset=ISO-8859-1 No, but to make changes to the standard it is quite obvious that being able to assess the impact is important. I showed this quite clearly, I think, using a few examples. But if there is a more suitable list where you discuss the methods and processes and tools used when working with C++ standard changes I can repost there. Den fredagen den 27:e september 2013 kl. 16:17:11 UTC+2 skrev Nevin ":-)" Liber: > > On 27 September 2013 04:40, Bengt Gustafsson > > wrote: > >> >> My suggestion is to work towards creating a tool that can do a >> statistical analysis of different potentially code breaking standard >> changes by scanning a large base of source code. >> > > Why is this in std-proposals? I see nothing here that needs to be > addressed by the C++ Standard. > -- > Nevin ":-)" Liber > (847) > 691-1404 > -- --- 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_761_17449934.1380330238042 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
No, but to make changes to the standard it is quite obviou= s that being able to assess the impact is important. I showed this quite cl= early, I think, using a few examples.

But if there is a = more suitable list where you discuss the methods and processes and tools us= ed when working with C++ standard changes I can repost there.

Den fredagen den 27:e september 2013 kl. 16:17:11 UTC+2 skrev Ne= vin ":-)" Liber:
On 27 September 2013 04:40, Bengt Gustafsson <bengt.gu...@beamways.com> wrote:
=

My suggestion is to work towards creating a tool that c= an do a statistical analysis of different potentially code breaking standar= d changes by scanning a large base of source code.

Why is this in std-proposals?  = I see nothing here that needs to be addressed by the C++ Standard.
--
 Nevin ":-)" Liber  <mailto:ne...@eviloverlord= ..com>  (847) 691-1404

--
 
---
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-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/<= /a>.
------=_Part_761_17449934.1380330238042-- .