[geos-devel] GEOS cross-heap problems

Sean Gillies sgillies at frii.com
Wed May 13 10:59:05 EDT 2009

On May 13, 2009, at 7:42 AM, Mateusz Loskot wrote:

> Frank Warmerdam wrote:
>> strk wrote:
>>> On Wed, May 13, 2009 at 12:19:23AM -0400, Frank Warmerdam wrote:
>>> Only, it'll have to stay (I've read Mateusz suggesting using
>>> type-specific destroyers).
>> I cannot imagine why a type specific destroyer would be needed
>> for simple malloc()/free() buffer allocations.
> Frank,
> But GEOS user does not know what allocator is hidden behind  
> GEOSGeomToWKT function and he does *not* need or want to know.
> GEOSFree exposes all the meat that is supposed be encapsulated
> and it makes GEOS C API not symmetric so confusing.

Aren't we supposed to be using the reader/writer API now? Add  
GEOSWK*Writer_Free functions (if we must) to those interfaces and  
GEOSFree to address the problem with deprecated GeomToWKT?


More information about the geos-devel mailing list