[geos-devel] Documentation

[Todd Vollmer]

I would suggest that the correct way to write a function that must return a
object is to have that function return a new object not a pointer to the
object. Yes you will incur some overhead for creation of the object but you
will at least guarantee a  consistent behaviour.

Todd V.

-----Original Message-----
From: David Blasby [mailto:dblasby at refractions.net]
Sent: Tuesday, October 07, 2003 3:33 PM
To: GEOS Development List
Subject: Re: [geos-devel] Documentation


strk wrote:

> Who is responsible for GEOS overall architecture ?

This would be Martin Davis, Yuri Bychkov, and Paul Ramsey.  But, its 
open source, so its really a community process.  If you have suggestions 
- just post them to the list.

 >PS: I will try adding an example.cpp file containing what I've
 >understood so far ...

Excellent!

Personally, I'm not too concerned about returning copies of object or 
the actual object (Although the latter has a big efficiency plus.).  We 
just need to be consistent and explicit.

I think PostGIS is the only real application using GEOS at the moment - 
and I'm willing to modify the POSTGIS->GEOS and GEOS->POSTGIS converters 
if necessary.

I'm actually really quite impressed with GEOS in PostGIS. I've been 
doing quite a bit of actual processing and checking using it!  Its so 
much easier to write simple SQL instead of Java (or worse C++) code to 
check data or actually process stuff.

Kudos to everyone involved!

dave


_______________________________________________
geos-devel mailing list
geos-devel at geos.refractions.net
http://geos.refractions.net/mailman/listinfo/geos-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/geos-devel/attachments/20031007/f84f9e00/attachment.html