This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/9073: Can __STL_ASSERTIONS come back, but with more than rope?
- From: bkoz at gcc dot gnu dot org
- To: 128993 at bugs dot debian dot org, asd at suespammers dot org, bkoz at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org
- Date: 2 Jan 2003 23:07:38 -0000
- Subject: Re: libstdc++/9073: Can __STL_ASSERTIONS come back, but with more than rope?
- Reply-to: bkoz at gcc dot gnu dot org, 128993 at bugs dot debian dot org, asd at suespammers dot org, bkoz at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot 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