public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "david.irvine at maidsafe dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56004] Possible bug with decltype and access modifer order
Date: Wed, 16 Jan 2013 16:41:00 -0000 [thread overview]
Message-ID: <bug-56004-4-opRJtqTbpS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56004-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56004
--- Comment #2 from David Irvine <david.irvine at maidsafe dot net> 2013-01-16 16:40:43 UTC ---
(In reply to comment #1)
> As was explained on stackoverflow, this has nothing t odo with access
> modifiers, as you can easily demonstrate by making everything public.
>
> _t has not been declared at the point where you try to use it, so the name is
> not in scope. What are you claiming is a bug?
It might be my confusion but is that not altering modifiers ? I am not sure why
the initialisation list does not make the private member available (at least
declared).
On the clang mailing list this was hinted at as well, but I am not sure that
this is a case where private: before public: does work and not vice versa
although as I said it is very likely a c++ issue that I have just not come
across yet (although I will remember as usual).
Can you confirm why the _t is not available or declared when it is in the
initialisation list ? does the decltype require earlier visibility than the ctr
?
Sorry if this is indeed not a bug but a misunderstanding.
next prev parent reply other threads:[~2013-01-16 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 15:13 [Bug c++/56004] New: " david.irvine at maidsafe dot net
2013-01-16 16:20 ` [Bug c++/56004] " redi at gcc dot gnu.org
2013-01-16 16:41 ` david.irvine at maidsafe dot net [this message]
2013-01-16 17:31 ` redi at gcc dot gnu.org
2013-01-16 18:17 ` david.irvine at maidsafe dot net
2013-01-16 18:26 ` redi 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-56004-4-opRJtqTbpS@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).