public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org To: 128993@bugs.debian.org, asd@suespammers.org, bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: libstdc++/9073: Can __STL_ASSERTIONS come back, but with more than rope? Date: Thu, 02 Jan 2003 23:07:00 -0000 [thread overview] Message-ID: <20030102230738.19941.qmail@sources.redhat.com> (raw) Synopsis: Can __STL_ASSERTIONS come back, but with more than rope? Responsible-Changed-From-To: unassigned->bkoz Responsible-Changed-By: bkoz Responsible-Changed-When: Thu Jan 2 15:07:37 2003 Responsible-Changed-Why: Mine. State-Changed-From-To: open->feedback State-Changed-By: bkoz State-Changed-When: Thu Jan 2 15:07:37 2003 State-Changed-Why: __STL_ASSERTIONS making a comeback is extremely unlikely. A better way to do this would be to just encapsulate std::vector and add your own runtime checks. I believe that Cay Horstman has done this with older versions of std::vector: you might check google. -benjamin http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9073
next reply other threads:[~2003-01-02 23:07 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-02 23:07 bkoz [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-10 18:03 neroden 2002-12-27 15:36 Matthias Klose
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=20030102230738.19941.qmail@sources.redhat.com \ --to=bkoz@gcc.gnu.org \ --cc=128993@bugs.debian.org \ --cc=asd@suespammers.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).