On Thu, May 12, 2011 at 11:50 AM, Sandro Santilli <s...@keybit.net> wrote: > > So both Python and Ruby made the "PreparedGeometry" type explicit. > > I was thinking more of a .prep() function returning void and internally > holding a prepared version to transparently use in all prepared-aware > methods. This would kind of follow PostGIS use, where you actually don't > even explicitly call the "prepare" which happens based on an heuristic > (the second time you run a predicate on a geometry that geometry gets > prepared). The advantage of transparency would be there's no API change > but automatic performance improvement. >
I'd be open to that sort of thing. I'm still in beta after all. _______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/geos-devel
