[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 104725] New: Warning in g++ is an error in kdevelop
From: kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date: 2005-04-28 18:23:51
Message-ID: 20050428202350.104725.crh15 () case ! edu
[Download RAW message or body]
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=104725
Summary: Warning in g++ is an error in kdevelop
Product: kdevelop
Version: 2.1.5
Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: kdevelop-bugs kdevelop org
ReportedBy: crh15 case edu
Version: 2.1.5 (using KDE 3.4.0, Debian Package 4:3.4.0-0ubuntu3.1 (3.1))
Compiler: gcc version 3.3.5 (Debian 1:3.3.5-8ubuntu2)
OS: Linux (i686) release 2.6.10-5-386
The following line of code:
std::list< item <AT> * >::iterator list_iter;
recieves the following warning from g++:
symtab.template: In member function `hamons::item<AT>*
SymTab<AT>::find(std::basic_string<char, std::char_traits<char>,
std::allocator<char> >)':
symtab.template:48: warning: `std::list<hamons::item<AT>*,
std::allocator<hamons::item<AT>*> >::iterator' is implicitly a typename
symtab.template:48: warning: implicit typename is deprecated, please see the
documentation for details
however in kdevelop 3.4 it recieves an error:
symtab.template:48: error: parse error before `;' token
Shouldn't these be consistant considering they are the same code one using kdevelop and one using g++?
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic