3 ms·
> Probably because people with experience know how to handle these things up front so that they don't occur. bla bla bla. especially if you are dealing with a
by MichaelMoser123 10y ago
> Probably because people with experience know how to handle these things up front so that they don't occur. bla bla bla.
especially if you are dealing with a large code base with shifting requirements, where the code has been written over a long time by a lot of people; in a real world system you just can't make these assumptions regarding 'skill' at all. Even skilled people will have to deal with issues like invalidated iterators / containers that have been modified in non obvious ways / lots of other goodies as well.
there are a lot of projects/products like this, my guess is that this is the case with the majority of projects.
- MichaelMoser123 10y agoanother example that i had the other day: lets say you have a cache of some sorts, now you keep adding entries to the cache without deleting them, in the end it blows up because it is out of memory. Now technically it is not a leak, but the result is that of a leak. Now good luck solving that with smart pointers and reference counting, etc.