public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tr3w at freemail dot hu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53725] New: Prototype does not match error if the definition of the ctor is separated from its declaration.
Date: Tue, 19 Jun 2012 23:47:00 -0000	[thread overview]
Message-ID: <bug-53725-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53725

             Bug #: 53725
           Summary: Prototype does not match error if the definition of
                    the ctor is separated from its declaration.
    Classification: Unclassified
           Product: gcc
           Version: 4.6.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: tr3w@freemail.hu


Created attachment 27657
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27657
Minimal example

In certain conditions if the definition of the ctor separated from its
declaration it generates an compiler error.

I created a minimal example. The original code is from Boost.Move.
Error:
testfull.cpp:16:1: error: prototype for ‘movable::movable(rv<movable>&)’ does
not match any in class ‘movable’
testfull.cpp:5:7: error: candidates are: movable::movable(const movable&)
testfull.cpp:13:5: error:                 movable::movable(rv<movable>&)


If the ctor definition is inside the class the code compiles.

The same can happen with the assignment operator as visible here:
http://lists.boost.org/Archives/boost/2011/07/184263.php


             reply	other threads:[~2012-06-19 23:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19 23:47 tr3w at freemail dot hu [this message]
2012-06-20  1:43 ` [Bug c++/53725] Prototype does not match error if the definition of the ctor is separated from its declaration and attributes redi at gcc dot gnu.org
2014-06-11 18:06 ` paolo.carlini at oracle dot com
2021-07-23  1:20 ` pinskia at gcc dot gnu.org

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=bug-53725-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).