c++/10086: static const int unresolved in ? : construct

Chris Kappler chrisk@mysticlabs.com
Sat Mar 15 17:03:00 GMT 2003


I do not agree.  In the attachment to this email, the commented code
compiles perfectly.  The uncommented code results in a linker error.  I
believe that the two pieces of code are semantically equivalent.

----- Original Message -----
From: <bangerth@dealii.org>
To: <chrisk@mysticlabs.com>; <gcc-bugs@gcc.gnu.org>; <gcc-prs@gcc.gnu.org>;
<nobody@gcc.gnu.org>
Sent: Friday, March 14, 2003 5:33 PM
Subject: Re: c++/10086: static const int unresolved in ? : construct


> Synopsis: static const int unresolved in ? : construct
>
> State-Changed-From-To: open->closed
> State-Changed-By: bangerth
> State-Changed-When: Fri Mar 14 22:33:31 2003
> State-Changed-Why:
>     Not a bug. You need a definition of the variable.
>
>
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p
r=10086
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bug.cpp
Type: application/octet-stream
Size: 574 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-bugs/attachments/20030315/4677ed8e/attachment.obj>


More information about the Gcc-bugs mailing list