Dinkumware: Turn on rigorous legality checking?

[Randall Parker]

Is there some way with the CG CB 2007 Dinkumware STL containers to turn on a slower and more rigorous checking of container operations to detect illegal operations?

I'm already using CodeGuard. I wonder if there are things that can be caught in operations on stl::vector, stl::map, etc that CodeGuard can't catch that the STL container authors can catch. Isn't there some way to turn on more checking? Or does one need a fancier version of Dinkumware's containers purchased from Dinkumware to get that capability?

[David Dean [CodeGear]]

Post by Randall Parker
Is there some way with the CG CB 2007 Dinkumware STL containers to turn on a
slower and more rigorous checking of container operations to detect illegal
operations?

Is this what you are referring to:

<http://blogs.codegear.com/ddean/2007/05/23/34808>

[unknown]

Post by David Dean [CodeGear]

Post by Randall Parker
Is there some way with the CG CB 2007 Dinkumware STL containers to turn on a
slower and more rigorous checking of container operations to detect illegal
operations?

<http://blogs.codegear.com/ddean/2007/05/23/34808>

Is this the only debug constant available for activation?
#define _HAS_ITERATOR_DEBUGGING 1

Or are there perhaps others?

[Alan Bellingham]

Randall Parker

Post by unknown
Is this the only debug constant available for activation?
#define _HAS_ITERATOR_DEBUGGING 1
Or are there perhaps others?

Out of curiosity, what other container debug assistance do you need? Or
is it not fine-grained enough?

(I suspect that the #define produces fatter iterators with references to
the containers they refer to. Once that's so, checking comparisons (are
the containers the same), and running past begin() or end() are both
possible and relatively trivial.)

Alan Bellingham

[Randall Parker]

Post by Alan Bellingham
Randall Parker

Post by unknown
Is this the only debug constant available for activation?
#define _HAS_ITERATOR_DEBUGGING 1
Or are there perhaps others?

Out of curiosity, what other container debug assistance do you
need? Or is it not fine-grained enough?

Alan,

I always want more even when I do not know what I want. :>

[David Dean [CodeGear]]

In article <4828eead$***@newsgroups.borland.com>,
Randall Parker

Post by unknown
Is this the only debug constant available for activation?
#define _HAS_ITERATOR_DEBUGGING 1
Or are there perhaps others?

That's the only one I'm aware of in the dinkumware STL.