[postgis-devel] Re-organising the PostGIS codebase - to liblwgeom or not liblwgeom?

[strk]

On Thu, Apr 24, 2008 at 08:26:18AM -0700, Paul Ramsey wrote:

> 2- liblwgeom, unsure, leaning negative
> 
> Some of the questions I have seen on the list about the wrappering of
> types, and my own reading of functions has made me less than enamoured
> of the abstraction layer.  The trouble is that is violates YAGNI (my
> new personal religion). No one has asked us for this, no one is using
> it *currently*, so why should we add complexity to our own code to
> support it?

My idea was it would have made contributing more functions easier.
Was initially more for still in-postgresql then outside.
See also the other mail about lwfree and the amount of memory it 
releases.

--strk;