[Bug libstdc++/34015] warning in backward_warning.h is illegible

2009-02-07 Thread manu at gcc dot gnu dot org
--- Comment #9 from manu at gcc dot gnu dot org 2009-02-07 14:44 --- Closing. Nobody cares enough to fix this in any other way and GCC 4.3.0 is out already. -- manu at gcc dot gnu dot org changed: What|Removed |Added ---

[Bug libstdc++/34015] warning in backward_warning.h is illegible

2008-08-26 Thread manu at gcc dot gnu dot org
--- Comment #8 from manu at gcc dot gnu dot org 2008-08-26 11:13 --- (In reply to comment #7) > The goal for warnings should be to use an attribute on the specific class or > function in question, not on a per-file basis. Care to elaborate? I don't understand what you mean here. > Unfo

[Bug libstdc++/34015] warning in backward_warning.h is illegible

2008-04-24 Thread bkoz at gcc dot gnu dot org
--- Comment #7 from bkoz at gcc dot gnu dot org 2008-04-24 17:27 --- The goal for warnings should be to use an attribute on the specific class or function in question, not on a per-file basis. Unfortunately this does not work at the moment. So, the backwards_warning.h file has been adj

[Bug libstdc++/34015] warning in backward_warning.h is illegible

2007-12-11 Thread bkoz at gcc dot gnu dot org
--- Comment #6 from bkoz at gcc dot gnu dot org 2007-12-11 21:48 --- Subject: Bug 34015 Author: bkoz Date: Tue Dec 11 21:48:16 2007 New Revision: 130778 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=130778 Log: 2007-12-11 Benjamin Kosnik <[EMAIL PROTECTED]> PR libstd

[Bug libstdc++/34015] warning in backward_warning.h is illegible

2007-11-19 Thread bkoz at gcc dot gnu dot org
-- bkoz at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |bkoz at gcc dot gnu dot org |dot org