Sign in to follow this  

On the benefits of using a checked STL implementation

This topic is 4392 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Another one of the new features of VS2005 is a checked STL implementation. Iterators and containers now perform bounds and sanity checking before and after use to determine improper usage. Despite using the STL regularly for three years, it highlighted two very silly mistakes that I would have otherwise missed on VS2003. Do yourself a favor and get decent code coverage under a checked STL implementation. The results may surprise you - and prevent a mysterious crash further down the road.

Share this post


Link to post
Share on other sites
So it does, awesome. From my simple test, the diagnostics are fairly useful as well.

Of course, that means that debug builds will be even more slow than they were before, which means people will be even more likely to naively discard the standard library as too slow without proper testing.

CM

Share this post


Link to post
Share on other sites

This topic is 4392 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this