public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/62169] map iterators under _GLIBCXX_DEBUG diverge
Date: Sun, 24 Aug 2014 10:35:00 -0000	[thread overview]
Message-ID: <bug-62169-4-hSXF9jOGbn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62169-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62169

--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
It's not an option IMHO. See http://www​.stroustrup.com/SCARY.pdf for the
benefits of the current design. Those benefits outweigh the advantage of having
non-portable code diagnosed. Debug iterators can't be SCARY because they have a
pointer back to their patent container so have to depend on the exact type.
>From gcc-bugs-return-459134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Aug 24 10:45:50 2014
Return-Path: <gcc-bugs-return-459134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17162 invoked by alias); 24 Aug 2014 10:45:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17111 invoked by uid 48); 24 Aug 2014 10:45:44 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/62169] map iterators under _GLIBCXX_DEBUG diverge
Date: Sun, 24 Aug 2014 10:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 4.8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-62169-4-ZLQbmrPtT6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-62169-4@http.gcc.gnu.org/bugzilla/>
References: <bug-62169-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-08/txt/msg01631.txt.bz2
Content-length: 394

https://gcc.gnu.org/bugzilla/show_bug.cgi?idb169

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #6)
> they have a pointer back to their patent container

s/patent/parent/

As for solving the problem of switching containers, use a typedef for the
container, or auto for the iterator. It doesn't need to be solved by the
compiler.


  parent reply	other threads:[~2014-08-24 10:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 12:53 [Bug libstdc++/62169] New: " terra at gnome dot org
2014-08-18 12:56 ` [Bug libstdc++/62169] " terra at gnome dot org
2014-08-18 12:56 ` terra at gnome dot org
2014-08-18 13:01 ` terra at gnome dot org
2014-08-23 23:37 ` redi at gcc dot gnu.org
2014-08-24  0:07 ` terra at gnome dot org
2014-08-24 10:35 ` redi at gcc dot gnu.org [this message]
2014-09-19 13:20 ` 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-62169-4-hSXF9jOGbn@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).