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.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
_______________________________________________
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel
