This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/34015] warning in backward_warning.h is illegible
- From: "manu at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 Aug 2008 11:13:39 -0000
- Subject: [Bug libstdc++/34015] warning in backward_warning.h is illegible
- References: <bug-34015-655@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla 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.
> Unfortunately this does not work at the moment. So, the backwards_warning.h
> file has been adjusted to make it a bit more clear as to what is going on, and
> what should be used for deprecated items.
I thought we handled newlines "\n" within strings given to #error. Is this
forbidden by any standard?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34015