Re: c++/924: -Wuninitialized does not seem to warn on uninitialize class members.

Re: c++/924: -Wuninitialized does not seem to warn on uninitialize class members.

[bangerth]

Synopsis: -Wuninitialized does not seem to warn on uninitialize class members.

State-Changed-From-To: analyzed->closed
State-Changed-By: bangerth
State-Changed-When: Sun Nov 10 12:29:10 2002
State-Changed-Why:
    You get the warning with -Weffc++:
    tmp/g> /home/bangerth/bin/gcc-3.3x-pre/bin/c++ -Weffc++ -c x.cc
    x.cc:1: warning: `class no_init' has pointer data members
    x.cc:1: warning:   but does not override `no_init(const no_init&)'
    x.cc:1: warning:   or `operator=(const no_init&)'
    x.cc: In constructor `no_init::no_init()':
    x.cc:7: warning: `no_init::ptr' should be initialized in the member
       initialization list

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=924

Re: c++/924: -Wuninitialized does not seem to warn on uninitialize class members.

[Wolfgang Bangerth]

The following reply was made to PR c++/924; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Neil Booth <neil@daikokuya.co.uk>
Cc: bangerth@dealii.org, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>,
   <mdejong@redhat.com>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/924: -Wuninitialized does not seem to warn on uninitialize
 class members.
Date: Sun, 10 Nov 2002 15:02:54 -0600 (CST)

 > > State-Changed-From-To: analyzed->closed
 > > State-Changed-Why:
 > >     You get the warning with -Weffc++:
 > 
 > Shouldn't -Wuninitialised warn too?  Or at least, document that this
 > case is not warned about?
 
 Maybe. But -Wuninitialized reads
 `-Wuninitialized'
      An automatic variable is used without first being initialized.
 and we are not talking about automatic variables, but a member variable.
 I should have stated this more clearly. (Also, there are good reasons to 
 initialize member variables later; -Wunitialized only covers the case 
 where a variable is actually _used_ uninitialized, but this as well is not 
 the case here.)
 
 > We shouldn't be too hasty to close bugs.
 
 I'd be happy to re-open the report if you want me to.
 
 Regards
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 

Re: c++/924: -Wuninitialized does not seem to warn on uninitialize class members.

[Neil Booth]

The following reply was made to PR c++/924; it has been noted by GNATS.

From: Neil Booth <neil@daikokuya.co.uk>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	mdejong@redhat.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/924: -Wuninitialized does not seem to warn on uninitialize class members.
Date: Sun, 10 Nov 2002 20:51:01 +0000

 bangerth@dealii.org wrote:-
 
 > Synopsis: -Wuninitialized does not seem to warn on uninitialize class members.
 > 
 > State-Changed-From-To: analyzed->closed
 > State-Changed-By: bangerth
 > State-Changed-When: Sun Nov 10 12:29:10 2002
 > State-Changed-Why:
 >     You get the warning with -Weffc++:
 >     tmp/g> /home/bangerth/bin/gcc-3.3x-pre/bin/c++ -Weffc++ -c x.cc
 >     x.cc:1: warning: `class no_init' has pointer data members
 >     x.cc:1: warning:   but does not override `no_init(const no_init&)'
 >     x.cc:1: warning:   or `operator=(const no_init&)'
 >     x.cc: In constructor `no_init::no_init()':
 >     x.cc:7: warning: `no_init::ptr' should be initialized in the member
 >        initialization list
 
 Shouldn't -Wuninitialised warn too?  Or at least, document that this
 case is not warned about?  We shouldn't be too hasty to close bugs.
 
 Neil.