Bug#128993: libstdc++/9073: Can __STL_ASSERTIONS come back, but with more than rope?
- 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: Bug#128993: libstdc++/9073: Can __STL_ASSERTIONS come back, but with more than rope?
- From: bkoz@gcc.gnu.org
- Date: 2 Jan 2003 23:07:38 -0000
- Message-id: <[🔎] 20030102230738.19941.qmail@sources.redhat.com>
- Reply-to: bkoz@gcc.gnu.org, 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, gcc-gnats@gcc.gnu.org, 128993@bugs.debian.org
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
Reply to: