220 4491 <4f08b8aa-79cd-45a7-8d7b-7dc4b380f5d1@isocpp.org> article Path: news.gmane.org!not-for-mail From: Nicol Bolas Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: using new keywords for more proposes Date: Thu, 23 May 2013 06:36:50 -0700 (PDT) Lines: 88 Approved: news@gmane.org Message-ID: <4f08b8aa-79cd-45a7-8d7b-7dc4b380f5d1@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_136_12758614.1369316210439" X-Trace: ger.gmane.org 1369316215 19377 80.91.229.3 (23 May 2013 13:36:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 23 May 2013 13:36:55 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCEKFTV6ZUMBB5NW7CGAKGQET4ZV25Q@isocpp.org Thu May 23 15:36:56 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-ob0-f197.google.com ([209.85.214.197]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UfVhP-0006Jy-8A for gclcip-std-proposals@m.gmane.org; Thu, 23 May 2013 15:36:56 +0200 Original-Received: by mail-ob0-f197.google.com with SMTP id dn14sf13541080obc.8 for ; Thu, 23 May 2013 06:36:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-beenthere:date:from:to:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe:content-type; bh=Fce9+q2ySupbgYKL6qiDBRiyb+N+mNfuUKtscpCges8=; b=YR4oAwkANi62HYxCwfx7Af2tRRzmpNUtF3G4QWveupg3o6KzkkTkOaCo3yGkwewTBh v0GEgt3EKeVyQ/JCyYdAwygtpJ2Ufq2IHT1rh6Xqn9ENCLfL62rfCmd0MO9oX4D0o0zF QVLlD7iykIELsgyCD18+nPPwaAihxPRmToaYeK3xT4BkYByDowzrvjgOZm0E35guJJQA TwwfSEa3keM18giGrGQ4oyrchVd0vK5Edu0e1eG2LUyLkn+sO9f1nZoTdShF4uaUiV0r sx5HU5wfexIP7hJ0rW7s1dgrijwlh2B2O/CmcRHyriIrDRrOF2dMOr8G8oBZd84uocsu K1DQ== X-Received: by 10.42.23.210 with SMTP id t18mr9666495icb.10.1369316214162; Thu, 23 May 2013 06:36:54 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.50.85.106 with SMTP id g10ls4078172igz.12.canary; Thu, 23 May 2013 06:36:51 -0700 (PDT) X-Received: by 10.50.114.36 with SMTP id jd4mr390292igb.14.1369316211915; Thu, 23 May 2013 06:36:51 -0700 (PDT) In-Reply-To: X-Original-Sender: jmckesson@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:4491 Archived-At: ------=_Part_136_12758614.1369316210439 Content-Type: text/plain; charset=ISO-8859-1 On Thursday, May 23, 2013 3:29:57 AM UTC-7, Ran Regev wrote: > > > Thanks for the answer, backward compatibility was my initial guess. > I have two following questions: > 1) Is it only me or that everyone must fix something when advancing a > compiler? > And if I'm not the only one, then what does it matter if we need to fix X > issues or X + 3? > Most legal C++ code compiles just fine under C++11. While there certainly are some issues that need fixing, you want to *minimize* those issues as much as possible. You don't just make changes willy-nilly and tell people to "fix it yourself". Doing that leads to people simply not adopting C++11. Just look at the "smoothness" of the transition from Python 2.x to Python 3.x. And by "transition", I mean "balkanization of the community". That's what happens if you don't try to minimize breaking changes. We're talking about a situation where the *only* thing you get from making them full-fledged keywords is *breaking code*. Why would you want to break code when you *don't* have to? 2) How do c++ editors color the new keywords? Do they try to understand the > meaning of the words and color it accordingly, or ?? > That's up to IDEs, not the standards committee. -- --- 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. ------=_Part_136_12758614.1369316210439 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thursday, May 23, 2013 3:29:57 AM UTC-7, Ran Regev wrote:

Thanks for the answe= r, backward compatibility was my initial guess.
I have two follow= ing questions:
1) Is it only me or that everyone must fix somethi= ng when advancing a compiler?
And if I'm not the only one, then w= hat does it matter if we need to fix X issues or X + 3?

Most legal C++ code compiles just fine under C++11. While the= re certainly are some issues that need fixing, you want to minimize = those issues as much as possible. You don't just make changes willy-nilly a= nd tell people to "fix it yourself". Doing that leads to people simply not = adopting C++11.

Just look at the "smoothness" of the transition from= Python 2.x to Python 3.x. And by "transition", I mean "balkanization of th= e community". That's what happens if you don't try to minimize breaking cha= nges.

We're talking about a situation where the only thing yo= u get from making them full-fledged keywords is breaking code. Why w= ould you want to break code when you don't have to?

2) How do c++ editors c= olor the new keywords? Do they try to understand the meaning of the words a= nd color it accordingly, or ??

That's = up to IDEs, not the standards committee.

--
 
---
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-pro= posals/?hl=3Den.
 
 
------=_Part_136_12758614.1369316210439-- .