This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] c++/2972 warn when ctor-initializer leaves uninitialized data

From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
To: Jason Merrill <jason at redhat dot com>
Cc: Jonathan Wakely <jwakely dot gcc at gmail dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>
Date: Mon, 7 Nov 2011 17:48:54 -0600
Subject: Re: [patch] c++/2972 warn when ctor-initializer leaves uninitialized data
References: <CAH6eHdRE9192yx6QU1GEQviQ5iSz5zUkNuaH8KJcoojmUDZnDQ@mail.gmail.com> <CAAiZkiA9JGxmjTqDk_4Yr8XvaCK-BaVFMtpv2X8x2cs-ZUnEeA@mail.gmail.com> <4EB85E39.9070009@redhat.com>

On Mon, Nov 7, 2011 at 4:39 PM, Jason Merrill <jason@redhat.com> wrote:
> On 11/07/2011 05:38 PM, Gabriel Dos Reis wrote:
>>>
>>> struct C
>>> {
>>> ?int i;
>>> ?C() = default;
>>> };
>>
>> so the defaulted constructor does not initialize C::i?
>
> No, it doesn't. ?value-initialization of a C will initialize it, but not
> default-initialization.
>

Thanks! (obvously I was stuck with earlier variation of the proposal.)

-- Gaby

References:
- [patch] c++/2972 warn when ctor-initializer leaves uninitialized data
  - From: Jonathan Wakely
- Re: [patch] c++/2972 warn when ctor-initializer leaves uninitialized data
  - From: Gabriel Dos Reis
- Re: [patch] c++/2972 warn when ctor-initializer leaves uninitialized data
  - From: Jason Merrill

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]