public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andysem at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/59325] Provide a way to disable deprecated warnings
Date: Thu, 28 Nov 2013 13:03:00 -0000	[thread overview]
Message-ID: <bug-59325-4-v8Z2uSyzBw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59325-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59325

--- Comment #4 from andysem at mail dot ru ---
(In reply to Jonathan Wakely from comment #3)
> Doing this before any other includes will work:
> 
> #include <bits/c++config>
> #undef _GLIBCXX_DEPRECATED
> #define _GLIBCXX_DEPRECATED
> 
> I'm not convinced we want to support this officially.

Yes, I'm doing something like that now, although I also have to detect that
we're using libstdc++. And I also have no easy way to add that code in every
.cpp file I have in my project, so I have to resort to -include command line
argument for gcc. That, in turn brings additional complications of detecting
which files need that tweak (i.e. C++ files) and which don't (i.e. C files). I
just think that all these hoops could be avoided if libstdc++ was a little more
friendly in this regard. After all, there's no harm in using e.g. auto_ptr in
C++11 code, it surely won't disappear from STL any time soon, so the warning is
a bit overreactive anyway.


  parent reply	other threads:[~2013-11-28 13:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28  8:40 [Bug libstdc++/59325] New: " andysem at mail dot ru
2013-11-28 11:14 ` [Bug libstdc++/59325] " redi at gcc dot gnu.org
2013-11-28 11:43 ` andysem at mail dot ru
2013-11-28 12:23 ` redi at gcc dot gnu.org
2013-11-28 13:03 ` andysem at mail dot ru [this message]
2014-12-21 11:10 ` redi at gcc dot gnu.org
2020-10-20 14:28 ` redi at gcc dot gnu.org
2020-10-20 14:32 ` redi at gcc dot gnu.org
2020-10-20 14:46 ` andysem at mail dot ru
2020-10-20 16:07 ` redi at gcc dot gnu.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=bug-59325-4-v8Z2uSyzBw@http.gcc.gnu.org/bugzilla/ \
    --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: link
Be 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).