uninitialized member warnings ?

Stephan Bergmann sbergman at redhat.com
Tue Sep 25 05:26:17 PDT 2012


On 09/25/2012 11:26 AM, Michael Meeks wrote:
> On Mon, 2012-09-24 at 20:17 +0100, Caolán McNamara wrote:
>> On Mon, 2012-09-24 at 11:55 -0400, Kohei Yoshida wrote:
>>> On Thu, Sep 20, 2012 at 7:02 AM, Michael Meeks <michael.meeks at suse.com> wrote:
>>>>          I've noticed a number of these straying in. Did we disable a warning on
>>>> un-initialized members for some reason ? I could swear the compiler used
>>>> to complain helpfully about this.
>>
>> Yeah, this was a recent cockup of mine when I did away with CUPSWrapper
>> and merged it into CUPSManager so master only
>
> 	Neato :-) the deeper question - as to why no warnings are popping out
> of the compiler for this when (surely) it's a trivial thing to check /
> warn for - is more concerning.
>
> 	Any gbuild experts have a view there ? :-)

There is no way for the compiler to decide this in general (unlike Java, 
C++ does not have restricting rules to allow the compiler to do so). 
Such a warning option has never been there AFAIK.

Stephan


More information about the LibreOffice mailing list