public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chsalvia at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/32408] Template Parsing Error Date: Tue, 19 Jun 2007 23:08:00 -0000 [thread overview] Message-ID: <20070619230801.22229.qmail@sourceware.org> (raw) In-Reply-To: <bug-32408-14723@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from chsalvia at gmail dot com 2007-06-19 23:08 ------- Sorry. It seems this is actually a namespace conflict issue. If you add include the iostream header file and add "using namespace std" the code will not compile, due to a conflict with std::count. #include <iostream> using namespace std; template <class T> struct templated_struct { int count; }; template <class T> int template_func() { templated_struct<T> s; if (s.count < 0) return 0; return 0; } int main() { template_func<int> (); return 0; } Now I'm not completely sure if this should be considered a bug. However, since count is clearly a member of templated_struct, there shouldn't be a namespace conflict here. Also, if you replace '<' with '>' or '==', it compiles fine with no namespace conflict, which means gcc seems to be confusing '<' with a template argument. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32408
next prev parent reply other threads:[~2007-06-19 23:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-06-19 20:22 [Bug c++/32408] New: " chsalvia at gmail dot com 2007-06-19 21:22 ` [Bug c++/32408] " schwab at suse dot de 2007-06-19 22:04 ` pcarlini at suse dot de 2007-06-19 23:08 ` chsalvia at gmail dot com [this message] 2007-06-19 23:10 ` pinskia at gcc dot gnu dot 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=20070619230801.22229.qmail@sourceware.org \ --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).