Thank you Robert and Charlie for your responses.
This is much clearer for me now.
Benjamin
Charlie Savage a écrit :
On 29/10/2007, *Benjamin Chartier* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Justin and Charlie, many thanks for your answers.
By the way, is there a ggod reason why the Reader and Writer API
should
be used in stead of the deprecated functions? Is there any
performance
issue?
You can do things like write EWKT/EWKB which aren't possible using
the old C API.
That's the most important thing. But also:
* the old api used global static variables for storing the byte order
and output dimensions. So on the off hand chance you wanted to write
out 2d and 3d outputs in 2 different threads you couldn't do it.
* the old api forced a creation of a new reader/writer each time you
called it. Probably not a big deal, but the new api let's you control
that so you can reuse the same reader/writer.
Hope that helps,
Charlie
_______________________________________________
geos-devel mailing list
geos-devel@geos.refractions.net
http://geos.refractions.net/mailman/listinfo/geos-devel
