http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21386
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
--- Additional Comments From bangerth at dealii dot org 2005-05-17 16:27
---
Discussing the exact wording is nitpicking. The problem is real so let's
confirm this PR.
W.
--
What|Removed |Added
-
--- Additional Comments From benh at bwsint dot com 2005-05-06 16:10
---
(In reply to comment #2)
> Note ICC causes the same thing in terms of error vs warning.
That'll be because ICC emulates gcc behaviour...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21386
--- Additional Comments From benh at bwsint dot com 2005-05-06 16:04
---
(In reply to comment #1)
> (In reply to comment #0)
> > The first error message is also odd; "non-lvalue" is C terminology that is
> > rarely used in relation to C++.
>
> That is wrong because the standard actually
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-05
05:17 ---
Note ICC causes the same thing in terms of error vs warning.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21386
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-04
18:34 ---
(In reply to comment #0)
> The first error message is also odd; "non-lvalue" is C terminology that is
> rarely used in relation to C++.
That is wrong because the standard actually uses lvalue and rvalue all
