public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "baiyang at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/42533]  New: boost_concept_check.h - _SGIAssignableConcept broken the class self contains
Date: Tue, 29 Dec 2009 10:23:00 -0000	[thread overview]
Message-ID: <bug-42533-18612@http.gcc.gnu.org/bugzilla/> (raw)

for example, I have a class like this:

class MyClass
{
public: 
    MyClass() ...
    MyClass(IN const MyClass& rhs) ...
    MyClass& operator=(IN const MyClass& rhs)...

private:
    typedef std::map< string, MyClass > KEYTBL; // Self contains
    struct PROP {
       ...
       KEYTBL tblKeys;
       ...
    };

    typedef SMART_POINTER< PROP > HPROP;
    HPROP m_hProp;
};

As the example shown, If with out (early and msvc) the boost concept check,
then everything is perfect ok, Because C++ will try to instantiation the map
only when we need to use it. BUT the boost conept check (_SGIAssignableConcept)
just broken the c++ delay instantiation rule, so everything is broken here.


-- 
           Summary: boost_concept_check.h - _SGIAssignableConcept broken the
                    class self contains
           Product: gcc
           Version: 4.3.2
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: baiyang at gmail dot com
  GCC host triplet: OpenSolaris 2009.06 x86
GCC target triplet: OpenSolaris 2009.06 x86


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


             reply	other threads:[~2009-12-29 10:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29 10:23 baiyang at gmail dot com [this message]
2009-12-29 10:43 ` [Bug c++/42533] " baiyang at gmail dot com
2009-12-29 10:56 ` [Bug libstdc++/42533] " paolo dot carlini at oracle dot com

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-42533-18612@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).