Article View: gnu.g++.bug
Article #912GCC 2.2.2: no error messages for uninitialized const's
From: Brendan Kehoe
Date: Sun, 06 Sep 1992 02:56
Date: Sun, 06 Sep 1992 02:56
28 lines
1143 bytes
1143 bytes
The next release of the compiler will report them properly:
foo.C:2: uninitialized const `o'
foo.C:3: uninitialized const `i'
foo.C:4: uninitialized const `p'
> Given the class declaration
>
> class c { public: int foo (void); };
>
> the declaration
>
> const c o;
>
> produces the error message
>
> stdin:2: uninitialized const `o'
>
> I would expect similar behavior for the declarations
>
> const int i;
> c * const p;
>
> but both pass without an error message.
--
Brendan Kehoe brendan@cygnus.com
Cygnus Support, Palo Alto, CA +1 415 322 3811
Technical Details
Message-ID:
<9209060256.AA21857@cygnus.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!cygnus.com!brendanReferences:
<19430@ector.cs.purdue.edu>Show Full Headers
Complete Article Headers
Newsgroups: gnu.g++.bug Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!cygnus.com!brendan From: brendan@cygnus.com (Brendan Kehoe) Subject: GCC 2.2.2: no error messages for uninitialized const's Message-ID: <9209060256.AA21857@cygnus.com> Sender: gnulists@ai.mit.edu Reply-To: brendan@cygnus.com Organization: GNUs Not Usenet References: <19430@ector.cs.purdue.edu> Distribution: gnu Date: Sun, 6 Sep 1992 02:56:51 GMT Approved: bug-g++@prep.ai.mit.edu Lines: 29