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

[Mark Cave-Ayland]

Obe, Regina wrote:

> 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.

Well, I know we wish to maintain compatibility as far as possible to 
encourage people to move from 1.3 to 1.4 when it comes out but there are 
already a couple of breaking changes in the pipeline such as GBT#93/96. 
As long as the changes are minor and well-documented (and we provide 
alternative functions for you to use) then I don't have an issue with 
this. Anyone upgrading to a new minor release should accept that the 
version number indicates small changes and should read the notes 
accordingly.


ATB,

Mark.

-- 
Mark Cave-Ayland
Sirius Corporation - The Open Source Experts
http://www.siriusit.co.uk
T: +44 870 608 0063