[geos-devel] GEOS Todo
David Blasby
dblasby at refractions.net
Tue May 27 19:02:32 EDT 2003
Norman Vine wrote:
> David Blasby writes:
>
>>There are two outstanding issues in GEOS:
>>
>>1. memory management. This is high priority.
>
>
> Using the c++ autoptr or a homegrown equivalant
> would help *alot* here
This is even more basic - if you delete any one Geometry you will
usually delete the PrecisionModel of *all* your Geometries.
There was discussion a little while ago about this when we first started
porting GEOS to PostGIS.
As it stands right now, you cannot delete *any* GEOS geometry or you're
royally screwed.
For catching the smaller leaks, a few people mentioned a really good
opensource memory-leak-fixer program. I cannot remember the name.
dave
ps. cf message with subjects;
"[geos-devel] problems with C/C++- getting warmer! (Reader Frees too
much?)"
"RE: [geos-devel] Status (New Example)"
"[geos-devel] WKTreader is broken"
"RE: [geos-devel] Deleting PrecisionModels"
More information about the geos-devel
mailing list