{snip}
Why should using the C standard lib's free() a bug?
Because just using free() on something that should be released with some
specific function assumes that that function is just a wrapper around free().
That might not be the case or might change over time. It also ignores the fact
that there can be multiple heap managements like on windows, when multiple
compiler versions (and therefore their RTL) are used.
Right, I get that. I was unaware of the issue
with different heap managements. Thanks for
pointing that one out.
Cheers,
Ben
Jürgen
--
Benjamin Ducke
{*} Geospatial Consultant
{*} GIS Developer
[email protected]
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
