220 7371 article Path: news.gmane.org!not-for-mail From: "Billy O'Neal" Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Re: Allowing "auto i =0, j;" Date: Sat, 19 Oct 2013 23:49:13 -0700 Lines: 168 Approved: news@gmane.org Message-ID: References: <0aa985aa-b557-4ce3-9a11-e6de9356c398@isocpp.org> <30a80118-16a9-4560-bbff-81a8a27d73d0@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0122aa2424b4bf04e9269327 X-Trace: ger.gmane.org 1382251792 21288 80.91.229.3 (20 Oct 2013 06:49:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2013 06:49:52 +0000 (UTC) Cc: thierry.seegers@gmail.com, fmatthew5876@gmail.com To: std-proposals Original-X-From: std-proposals+bncBDKLBLVE6ADBBEP2RWJQKGQETGHD2GQ@isocpp.org Sun Oct 20 08:49:57 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-oa0-f72.google.com ([209.85.219.72]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VXmpo-00060o-03 for gclcip-std-proposals@m.gmane.org; Sun, 20 Oct 2013 08:49:56 +0200 Original-Received: by mail-oa0-f72.google.com with SMTP id m17sf12079312oag.7 for ; Sat, 19 Oct 2013 23:49:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc: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=yvlzVlPiVSDxmyeCmkXVG8ZzpPkOvulEXQFi3onzr/w=; b=CVoO7K6BpBBrU55Cpvs0/tgF3ocyOAU2d9Hm7+eswaqEHJmCMn5FogWOIIOM1GJKIy s3qn3ul3ILoaN8EApn6Nmlvt46emNN9fWnkiLEgRxh8BCfoArUqu4R3XBEA3ApUZnDZm XNr+Xv3+Hq8jKUsnyOj6K3XyNpcG0xGTXS0CLSVL0Iag5MD2Gz6jY0I9RfFPMyJkzXP+ jGsJ0XwX44l4ZA8GN4B3GWwu2UzgUXhwydn+PsDVMZYVeOJ56zXkpjSCt/FECeD8LnJ2 hslEpw6zuolDjib5Oe8gk0HOXsqe/9pkDPP7/NsJnwno5OHAF8BMECqK8CZ/cs3mMVZD sIFQ== X-Received: by 10.182.118.194 with SMTP id ko2mr4236591obb.32.1382251794752; Sat, 19 Oct 2013 23:49:54 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.182.24.194 with SMTP id w2ls695174obf.20.gmail; Sat, 19 Oct 2013 23:49:53 -0700 (PDT) X-Received: by 10.60.134.230 with SMTP id pn6mr102493oeb.52.1382251793687; Sat, 19 Oct 2013 23:49:53 -0700 (PDT) Original-Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [2607:f8b0:4003:c02::233]) by mx.google.com with ESMTPS id sy1si8346961obc.90.2013.10.19.23.49.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 19 Oct 2013 23:49:53 -0700 (PDT) Received-SPF: pass (google.com: domain of billy.oneal@gmail.com designates 2607:f8b0:4003:c02::233 as permitted sender) client-ip=2607:f8b0:4003:c02::233; Original-Received: by mail-oa0-f51.google.com with SMTP id h1so3003084oag.10 for ; Sat, 19 Oct 2013 23:49:53 -0700 (PDT) X-Received: by 10.182.181.34 with SMTP id dt2mr14837353obc.30.1382251793526; Sat, 19 Oct 2013 23:49:53 -0700 (PDT) Original-Received: by 10.182.87.37 with HTTP; Sat, 19 Oct 2013 23:49:13 -0700 (PDT) In-Reply-To: X-Original-Sender: billy.oneal@gmail.com X-Original-Authentication-Results: mx.google.com; spf=pass (google.com: domain of billy.oneal@gmail.com designates 2607:f8b0:4003:c02::233 as permitted sender) smtp.mail=billy.oneal@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:7371 Archived-At: --089e0122aa2424b4bf04e9269327 Content-Type: text/plain; charset=ISO-8859-1 However, I could easily see someone expecting the type of j to be char const *. Billy O'Neal https://github.com/BillyONeal/ http://stackoverflow.com/users/82320/billy-oneal Malware Response Instructor - BleepingComputer.com On Sat, Oct 19, 2013 at 9:28 PM, ts wrote: > What Vlad said, it's the same compiler error as this: > > int i = 0, j = "hello"; > > > On Saturday, October 19, 2013 9:11:52 AM UTC-7, fmatth...@gmail.com wrote: >> >> I'm not sure this feature makes sense. >> >> Whats the type supposed to be in this cases? >> >> auto i = 0, j = 1L: >> >> On Friday, October 18, 2013 8:52:30 PM UTC-4, ts wrote: >>> >>> Hi all, >>> >>> I've found myself doing something like the following a lot in the past: >>> >>> int i = 0, j; >>> >>> And, naturally, I caught myself doing this recently: >>> >>> auto i = 0, j; >>> >>> About which the compiler complained since, AFAICT, it is explicitly >>> disallowed. I'm curious to know why. It doesn't seem that much of a stretch >>> to expect that j's type would be decltype(i)... >>> >>> Thanks for any insight about this! >>> >>> TS >>> >>> >>> -- > > --- > 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/. > -- --- 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/. --089e0122aa2424b4bf04e9269327 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
However, I could easily see someone expecting the type of = j to be char const *.

Billy O'Neal
https://github.com/BillyONeal/
Mal= ware Response Instructor - BleepingComputer.com


On Sat, Oct 19, 2013 at 9:28 PM, ts <thierry.seegers@gmail.com> wrote:
What Vlad said, it's the same compiler error as this:<= br>
<= div> int i =3D 0, j =3D "he= llo";


On Saturday, Octob= er 19, 2013 9:11:52 AM UTC-7, fmatth...@gmail.com wrote:
I'm not sure this feature makes sense.
=
Whats the type supposed to be in this cases?

a= uto i =3D 0, j =3D 1L:

On Friday, October 18, 2013 8:52:30 PM= UTC-4, ts wrote:
Hi all,

I've found myself doing something like = the following a lot in the past:

i= nt i =3D 0= , j;

And, naturally, I caught myself doing t= his recently:

auto i =3D 0, j;

About which the compiler complained since, AFAICT, it is e= xplicitly disallowed. I'm curious to know why. It doesn't seem that= much of a stretch to expect that j's type would be decltype(i)...

Thanks for any insight about this!

TS

--
=A0
---
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/gro= up/std-proposals/.

--
 
---
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>.
--089e0122aa2424b4bf04e9269327-- .