[geos-devel] GEOS, Shapely, DLLs, and memory

[Paul Ramsey]

In that case, Aron, can you put your GEOS patch into a Trac issue
(http://trac.osgeo.org/geos) for us to put into the next release.

Thanks,

P.

On Mon, Apr 27, 2009 at 12:46 PM, Charlie Savage <cfis at savagexi.com> wrote:
>
>
> Paul Ramsey wrote:
>>
>> On Mon, Apr 27, 2009 at 11:47 AM, Aron Bierbaum <aronbierbaum at gmail.com>
>> wrote:
>>
>>> I have attached a patch for both GEOS and Shapely that we have been
>>> testing with for a few weeks without any problems. Does anyone have a
>>> better way to address this issue?
>>
>> Pretty simple patch... more C-API changes. Hmm. Perhaps GEOS 3.2 will
>> be out sooner than one might expect.
>>
>> I don't have the smarts to know if there's a better way.
>
> There isn't.  For every piece of memory GEOS allocates and returns via the
> capi (or C++ api), it must provide a function to free it.
>
> If you are using C++ you can get around it by providing a memory deallocator
> for objects returned from GEOS (say for std::string in this case) but for C
> you obviously can't do that.
>
> Charlie
>
>
> --
> Charlie Savage
> http://cfis.savagexi.com
>
> _______________________________________________
> geos-devel mailing list
> geos-devel at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geos-devel
>