[postgis-devel] Public/Private API, ST_*/_ST_*

[Obe, Regina]

hmm I use those functions in some code I have.  So that would be kind of breaking in a major way for me.

Besides there is no counterpart to those particular functions in an obvious sense like _ST_Intersects
so some of those functions I consider a bit fuzzy as to whether they should be considered private except they are not documented.

-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net on behalf of Paul Ramsey
Sent: Mon 1/19/2009 11:43 PM
To: PostGIS Development Discussion
Subject: [postgis-devel] Public/Private API, ST_*/_ST_*
 
Unfortunately, when we function re-named things for 1.2, things got a  
little out-of-hand, and every single function ended up with an ST_*  
sibling. I'd like to back away from that a bit now, and flip private  
functions into _ST_* space.  Some examples are st_geom_accum,  
st_unite_garray, etc.  I'd like to do it without leaving the old  
variants around. This is "breaking", but since the functions are  
private, hopefully not actually breaking.

P.

--
Paul Ramsey
OpenGeo - http://opengeo.org
Putting the "Po" in "PostGIS".

_______________________________________________
postgis-devel mailing list
postgis-devel at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel



-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20090119/78f2c683/attachment.html>