public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53225] static operator new in multiple inheritance carries incorrect type information for the class Date: Fri, 04 May 2012 20:35:00 -0000 [thread overview] Message-ID: <bug-53225-4-ucJ53QvNHk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53225-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53225 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |INVALID --- Comment #15 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-05-04 20:35:12 UTC --- (In reply to comment #14) > I went through the life time issues in detail in prior comments. Yes, but you don't seem to understand C++, as evidenced by statements like "The operator, which has been copied into the child via inheritance, i.e. the child's version of the operator" > The C++ rules > for life time of an instance do not apply to those of the life time of a class. Classes don't have a lifetime - I don't know what you're talking about. > Or are you saying these are not distinct? For what reason is static type > information known at compile time not available to operator new - which is > called at run time? The static type of what? In "A::operator new" the name "this_type" refers to A::this_type. > Also, if operator new is to be an such an exception that static type > information can not be accessed in it, as it can be in every other operator or > method - then why doesn't the compiler say anything about it? Should there not > be a warning or some sort that an artificial constraint is being applied in > order to satisfy someone's interpretation of object lifetimes according to the > standard? operator new isn't an exception, all member functions work like that. This report is invalid. Please find somewhere else to learn C++, stackoverflow is a good place for it, but reporting compiler bugs isn't the right way to improve your understanding of the language.
next prev parent reply other threads:[~2012-05-04 20:35 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-04 3:30 [Bug c++/53225] New: " dimitrisdad at gmail dot com 2012-05-04 3:35 ` [Bug c++/53225] " dimitrisdad at gmail dot com 2012-05-04 3:41 ` pinskia at gcc dot gnu.org 2012-05-04 5:21 ` dimitrisdad at gmail dot com 2012-05-04 8:55 ` redi at gcc dot gnu.org 2012-05-04 9:44 ` redi at gcc dot gnu.org 2012-05-04 18:12 ` dimitrisdad at gmail dot com 2012-05-04 18:32 ` redi at gcc dot gnu.org 2012-05-04 18:57 ` dimitrisdad at gmail dot com 2012-05-04 19:25 ` dimitrisdad at gmail dot com 2012-05-04 19:45 ` redi at gcc dot gnu.org 2012-05-04 19:59 ` dimitrisdad at gmail dot com 2012-05-04 20:02 ` dimitrisdad at gmail dot com 2012-05-04 20:10 ` daniel.kruegler at googlemail dot com 2012-05-04 20:18 ` dimitrisdad at gmail dot com 2012-05-04 20:35 ` redi at gcc dot gnu.org [this message] 2012-05-04 20:56 ` dimitrisdad at gmail dot com 2012-05-04 20:59 ` redi at gcc dot gnu.org 2012-05-04 21:07 ` redi at gcc dot gnu.org 2012-05-04 21:16 ` dimitrisdad at gmail dot com 2012-05-04 21:27 ` dimitrisdad at gmail dot com 2012-05-04 21:30 ` redi at gcc dot gnu.org 2012-05-04 21:41 ` dimitrisdad at gmail dot com 2012-05-04 21:52 ` redi at gcc dot gnu.org 2012-05-04 21:56 ` redi at gcc dot gnu.org 2012-05-04 22:01 ` dimitrisdad at gmail dot com 2012-05-04 22:05 ` daniel.kruegler at googlemail dot com 2012-05-04 22:07 ` pinskia at gcc dot gnu.org 2012-05-04 22:09 ` redi at gcc dot gnu.org 2012-05-04 22:31 ` dimitrisdad at gmail dot com 2012-05-04 22:55 ` dimitrisdad at gmail dot com 2012-05-04 23:21 ` redi at gcc dot gnu.org 2012-05-04 23:37 ` dimitrisdad at gmail dot com 2012-05-04 23:37 ` dimitrisdad at gmail dot com 2012-05-05 0:04 ` pinskia at gcc dot gnu.org 2012-05-05 0:15 ` redi at gcc dot gnu.org 2012-05-05 0:49 ` dimitrisdad at gmail 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-53225-4-ucJ53QvNHk@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: linkBe 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).