public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chris at bubblescope dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/31247] std::vector::iterator::value_type is accessible Date: Sun, 09 Mar 2008 20:29:00 -0000 [thread overview] Message-ID: <20080309202832.15901.qmail@sourceware.org> (raw) In-Reply-To: <bug-31247-1902@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from chris at bubblescope dot net 2008-03-09 20:28 ------- Sorry to be pedantic, but could this be added to _GLIBCXX_DEBUG_PEDANTIC. I've previously tended to assume that _GLIBCXX_DEBUG should change only flag code that should fail in non-debug mode, but fails to be detected, whereas _GLIBCXX_DEBUG_PEDANTIC ensures that the code is standards compliant. On another note, could this be added when just -pedantic is added? I think it's a useful flag to add, I'm just trying to avoid having to change a bunch of working, although non standards-complaint code :) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31247
next prev parent reply other threads:[~2008-03-09 20:29 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-17 16:52 [Bug libstdc++/31247] New: " sylvain dot pion at sophia dot inria dot fr 2007-03-17 17:00 ` [Bug libstdc++/31247] " pinskia at gcc dot gnu dot org 2007-03-17 17:19 ` chris at bubblescope dot net 2007-03-17 17:35 ` sylvain dot pion at sophia dot inria dot fr 2007-03-17 17:52 ` chris at bubblescope dot net 2007-04-17 15:48 ` chris at bubblescope dot net 2007-04-17 16:04 ` pcarlini at suse dot de 2008-03-09 15:52 ` jwakely dot gcc at gmail dot com 2008-03-09 15:53 ` jwakely dot gcc at gmail dot com 2008-03-09 20:29 ` chris at bubblescope dot net [this message] [not found] <bug-31247-4@http.gcc.gnu.org/bugzilla/> 2011-10-28 9:32 ` marc.glisse at normalesup dot org 2011-10-28 9:41 ` paolo.carlini at oracle dot com 2011-10-28 9:58 ` redi at gcc dot gnu.org 2011-10-28 10:20 ` marc.glisse at normalesup dot org 2011-10-29 4:24 ` sylvain.pion at sophia dot inria.fr 2014-09-19 10:33 ` redi at gcc dot gnu.org 2014-09-19 11:37 ` glisse 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=20080309202832.15901.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).