public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "benoit dot hudson at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/34015] warning in backward_warning.h is illegible Date: Thu, 08 Nov 2007 15:35:00 -0000 [thread overview] Message-ID: <20071108153504.32761.qmail@sourceware.org> (raw) In-Reply-To: <bug-34015-655@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from benoit dot hudson at gmail dot com 2007-11-08 15:35 ------- The fact that the error appears in backward_warning.h is another annoyance, which is probably why the overly long descriptive message is there. Better would be that #include <ext/hash_set> would only report "<ext/hash_set> is deprecated; please use <hash_set> instead." Then the file listed as generating the problem is hash_set included from the user's code, and the message specifically says what's wrong, and the message fits on one line in a standard terminal. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34015
next prev parent reply other threads:[~2007-11-08 15:35 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-11-07 17:41 [Bug c++/34015] New: " benoit dot hudson at gmail dot com 2007-11-08 10:56 ` [Bug c++/34015] " manu at gcc dot gnu dot org 2007-11-08 11:23 ` Gabriel Dos Reis 2007-11-08 11:05 ` pcarlini at suse dot de 2007-11-08 11:23 ` gdr at cs dot tamu dot edu 2007-11-08 13:13 ` manu at gcc dot gnu dot org 2007-11-08 15:35 ` benoit dot hudson at gmail dot com [this message] 2007-11-20 6:03 ` [Bug libstdc++/34015] " bkoz at gcc dot gnu dot org 2007-12-11 21:48 ` bkoz at gcc dot gnu dot org 2008-04-24 17:28 ` bkoz at gcc dot gnu dot org 2008-08-26 11:15 ` manu at gcc dot gnu dot org 2009-02-07 14:44 ` manu 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=20071108153504.32761.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).