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: PR c++/25811

From: Fabien CHÊNE <fabien dot chene at gmail dot com>
To: Manuel López-Ibáñez <lopezibanez at gmail dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Mon, 5 Apr 2010 23:19:03 +0200
Subject: Re: PR c++/25811
References: <j2z8640d6051003310517h369aa01dke5adf4d9a3816288@mail.gmail.com> <x2w8640d6051003310522z2695885bz16e3ad5b4f4e43b1@mail.gmail.com> <n2z8640d6051003310709g6ca97636ua21ddaf0cfde25af@mail.gmail.com> <x2g6c33472e1003310733hc967f1f5uc0800189c85f9071@mail.gmail.com> <g2p8640d6051003310924n6ab516faz4a8952ef803fb40b@mail.gmail.com> <q2i8640d6051004051413p591379f9k662e1f8cf467f297@mail.gmail.com>

2010/4/5 Fabien CHÊNE <fabien.chene@gmail.com>:
> 2010/3/31 Fabien CHÊNE <fabien.chene@gmail.com>:
>> 2010/3/31 Manuel López-Ibáñez <lopezibanez@gmail.com>:
>>> So what happens when there is more than one? how would the user know
>>> which member is uninitialized?
>>
>> The diagnostic is approximately the same than for:
>>
>> struct A { int const i; };
>> void f() { A a; }
>>
>> I admit than we can do better for both cases.
>>
>>> More importantly, how would the user know where this member is declared?
>>> The error could provide a bit more information to the user.
>>
>> I will try to improve that.
>
> I have improved diagnostics in the attached patch.
> regested on x86_64-unknown-linux-gnu. OK for 4.6 ?

Updated patch with a correct ChangeLog entry and an updated
copyright's date in cp-tree.h

--
Fab

Attachment: pr25811.patch
Description: Binary data

Follow-Ups:
- Re: PR c++/25811
  - From: Jason Merrill

References:
- Re: PR c++/25811
  - From: Fabien CHÊNE

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