mike3 wrote:
I just found out that the iterators used by std::vector<> are not
required to perform boundschecking, even as a debug mode! So then what
do I do? I'd like to have it available as a debug, even if not in a
release version.
You should probably find a decent implementation of the Standard
library. Or just tweak yours.
For example, consider the piece of code at the end of this message.
Should I use a boundscheck in there to check whether or not the ranges
specified are in-bounds or out-of-bounds? But if I do, then it makes
that seemingly nice piece of code real messy and I don't like it so
much.
The implementation (and essentially the design) comes from the set
of requirements. Do your requirements include checking bounds in
the release mode? Can bounds be ignored by the users of your class
(even if it's you)? If they can (and essentially allowed to) and
you want to make your program robust enough to withstand those
"attacks" on the boundaries, then you _have_to_ check them yourself.
If you don't want to check and instead need to rely on the client's
code to check the bounds, then you need to document that crossing
the boundaries has undefined behaviour (just like the Standard says)
and put the burden of dealing with UB on the client.
[..]
V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask
on the debug options when using glibc/gcc. I remember finding out