public inbox for
help / color / mirror / Atom feed
Subject: Re: c++/10827: member function pointer array link problem
Date: Fri, 16 May 2003 22:16:00 -0000	[thread overview]
Message-ID: <> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]

Synopsis: member function pointer array link problem

State-Changed-From-To: open->closed
State-Changed-By: bajo
State-Changed-When: Fri May 16 22:16:23 2003
    Not a bug. ISO C++ standard mandates that you must always
    define static const member variables, even if initialized
    at declaration time. Quoting §9.4.2p4: "If a static data 
    member is of const integral or const enumeration type,
    its declaration in the class definition can specify a 
    constant-initializer which shall be an integral constant
    expression. [...] The member shall still be defined in a
    namespace scope if it is used in the program and the 
    namespace scope definition shall not contain an initializer."
    This leads us to the second problem of your code: ISO C++
    allows in-class initialization only for static const member
    of integral or enumeration type. In your case, the member
    type is neither integral or enumeration, so the code is
    ill-formed. It used to be accepted for a GCC extension
    (if you try to compile with -pedantic, you get a warning
    about it), but the extension has been removed already in
    GCC 3.3. I suggest to update your code to reflect this
    (just initialize the member at namescope definition).

             reply	other threads:[~2003-05-16 22:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 22:16 giovannibajo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-16 21:46 andre.maute

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).