220 11484 <349eba3f-0165-477b-bb4a-9aa5fc685af3@isocpp.org> article
Path: news.gmane.org!not-for-mail
From: Stack Machine <stackmachine@hotmail.com>
Newsgroups: gmane.comp.lang.c++.isocpp.proposals
Subject: Re: Controversy and debate: Uninitialized variables
 by default is a bug
Date: Tue, 17 Jun 2014 09:05:16 -0700 (PDT)
Lines: 71
Approved: news@gmane.org
Message-ID: <349eba3f-0165-477b-bb4a-9aa5fc685af3@isocpp.org>
References: <60caa4ef-b32d-40fe-97b6-8918fbb2bd51@isocpp.org>
Reply-To: std-proposals@isocpp.org
NNTP-Posting-Host: plane.gmane.org
Mime-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_211_3110880.1403021116359"
X-Trace: ger.gmane.org 1403021129 11958 80.91.229.3 (17 Jun 2014 16:05:29 GMT)
X-Complaints-To: usenet@ger.gmane.org
NNTP-Posting-Date: Tue, 17 Jun 2014 16:05:29 +0000 (UTC)
To: std-proposals@isocpp.org
Original-X-From: std-proposals+bncBDC7BQ4GSIMRBPOOQGOQKGQET76OLDI@isocpp.org Tue Jun 17 18:05:19 2014
Return-path: <std-proposals+bncBDC7BQ4GSIMRBPOOQGOQKGQET76OLDI@isocpp.org>
Envelope-to: gclcip-std-proposals@m.gmane.org
Original-Received: from mail-ie0-f200.google.com ([209.85.223.200])
	by plane.gmane.org with esmtp (Exim 4.69)
	(envelope-from <std-proposals+bncBDC7BQ4GSIMRBPOOQGOQKGQET76OLDI@isocpp.org>)
	id 1Wwvst-0000rJ-5f
	for gclcip-std-proposals@m.gmane.org; Tue, 17 Jun 2014 18:05:19 +0200
Original-Received: by mail-ie0-f200.google.com with SMTP id tr6sf42973237ieb.11
        for <gclcip-std-proposals@m.gmane.org>; Tue, 17 Jun 2014 09:05:18 -0700 (PDT)
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:x-original-sender:reply-to:precedence
         :mailing-list:list-id:list-post:list-help:list-archive
         :list-subscribe:list-unsubscribe:content-type;
        bh=vWLpOL2VtsEBNkcBYX20nn53vAEbDcvDBaBMepbmASc=;
        b=G0N3ee7JtX0s6eDCYN9y5/3Iaui4UT4B2BfnDM1L/maFi9hqfuYUFpdHJuqPtpMgXz
         u8oMNHyWWCe9y+LHX0RHpPneAL6c16yCYFf/Le9YTBzzHdAoH9eoRoll2S2YpQKoBalQ
         skidQ+866Wt/2Iz5Y7zYlEEchAdKnaqa5q4TTo76uAOiPZ0YKtUA9RIPfDwmjxzonMnk
         XBrMPBN4ycDbHrQLavQphJbJcfEK+Bg6IA/sVW9FoCD7p69f7z+47n2seLgSAYjRMmX3
         7RfVKQnbea9+uW06FwdOMTaaozxlNtsCR92HVT5pW8N9vVIP0HzHYNUTnXJbvdRfKwnX
         nDGg==
X-Gm-Message-State: ALoCoQnIJ8i/2+zK1e3WN+a+mucg3lLHJKQLhC23KREX63Oi7f3nEoGfge7vxV51iM3WQusMJ4wb
X-Received: by 10.50.56.74 with SMTP id y10mr662110igp.3.1403021118244;
        Tue, 17 Jun 2014 09:05:18 -0700 (PDT)
X-BeenThere: std-proposals@isocpp.org
Original-Received: by 10.140.88.80 with SMTP id s74ls593013qgd.50.gmail; Tue, 17 Jun
 2014 09:05:17 -0700 (PDT)
X-Received: by 10.140.29.4 with SMTP id a4mr30376qga.29.1403021117575;
        Tue, 17 Jun 2014 09:05:17 -0700 (PDT)
In-Reply-To: <60caa4ef-b32d-40fe-97b6-8918fbb2bd51@isocpp.org>
X-Original-Sender: stackmachine@hotmail.com
Precedence: list
Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org
List-ID: <std-proposals.isocpp.org>
X-Google-Group-Id: 399137483710
List-Post: <http://groups.google.com/a/isocpp.org/group/std-proposals/post>, <mailto:std-proposals@isocpp.org>
List-Help: <http://support.google.com/a/isocpp.org/bin/topic.py?topic=25838>, <mailto:std-proposals+help@isocpp.org>
List-Archive: <http://groups.google.com/a/isocpp.org/group/std-proposals/>
List-Subscribe: <http://groups.google.com/a/isocpp.org/group/std-proposals/subscribe>,
 <mailto:std-proposals+subscribe@isocpp.org>
List-Unsubscribe: <http://groups.google.com/a/isocpp.org/group/std-proposals/subscribe>,
 <mailto:googlegroups-manage+399137483710+unsubscribe@googlegroups.com>
Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:11484
Archived-At: <http://permalink.gmane.org/gmane.comp.lang.c++.isocpp.proposals/11484>

------=_Part_211_3110880.1403021116359
Content-Type: text/plain; charset=UTF-8

I think that both sides have some compelling arguments. How about this:
int i; // compiletime error: no initializer
int i = 0; // initialize to 0
int i = void; // ok, explicitly uninitialized
Yes, this does break backwards compatibility, but in a way that produces a 
compiletime error. Conversion tools shouldn't be too hard to write either.

-- 

--- 
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_211_3110880.1403021116359
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think that both sides have some compelling arguments. Ho=
w about this:<br><div class=3D"prettyprint" style=3D"background-color: rgb(=
250, 250, 250); border-color: rgb(187, 187, 187); border-style: solid; bord=
er-width: 1px; word-wrap: break-word;"><code class=3D"prettyprint"><div cla=
ss=3D"subprettyprint"><span style=3D"color: #008;" class=3D"styled-by-prett=
ify">int</span><span style=3D"color: #000;" class=3D"styled-by-prettify"> i=
</span><span style=3D"color: #660;" class=3D"styled-by-prettify">;</span><s=
pan style=3D"color: #000;" class=3D"styled-by-prettify"> </span><span style=
=3D"color: #800;" class=3D"styled-by-prettify">// compiletime error: no ini=
tializer</span><span style=3D"color: #000;" class=3D"styled-by-prettify"><b=
r></span><span style=3D"color: #008;" class=3D"styled-by-prettify">int</spa=
n><span style=3D"color: #000;" class=3D"styled-by-prettify"> i </span><span=
 style=3D"color: #660;" class=3D"styled-by-prettify">=3D</span><span style=
=3D"color: #000;" class=3D"styled-by-prettify"> </span><span style=3D"color=
: #066;" class=3D"styled-by-prettify">0</span><span style=3D"color: #660;" =
class=3D"styled-by-prettify">;</span><span style=3D"color: #000;" class=3D"=
styled-by-prettify"> </span><span style=3D"color: #800;" class=3D"styled-by=
-prettify">// initialize to 0</span><span style=3D"color: #000;" class=3D"s=
tyled-by-prettify"><br></span><span style=3D"color: #008;" class=3D"styled-=
by-prettify">int</span><span style=3D"color: #000;" class=3D"styled-by-pret=
tify"> i </span><span style=3D"color: #660;" class=3D"styled-by-prettify">=
=3D</span><span style=3D"color: #000;" class=3D"styled-by-prettify"> </span=
><span style=3D"color: #008;" class=3D"styled-by-prettify">void</span><span=
 style=3D"color: #660;" class=3D"styled-by-prettify">;</span><span style=3D=
"color: #000;" class=3D"styled-by-prettify"> </span><span style=3D"color: #=
800;" class=3D"styled-by-prettify">// ok, explicitly uninitialized</span><s=
pan style=3D"color: #000;" class=3D"styled-by-prettify"><br></span></div></=
code></div>Yes, this does break backwards compatibility, but in a way that =
produces a compiletime error. Conversion tools shouldn't be too hard to wri=
te either.<br></div>

<p></p>

-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />

------=_Part_211_3110880.1403021116359--

.
