[postgis-devel] Function Naming

[Obe, Regina]

Paul,
You realize this is not a complete list.  A cursory glance looks like
you left out all the long transaction support functions.

Also all those geometry_ functions you kept, I would prefer they don't
start with geometry. 

-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Paul
Ramsey
Sent: Friday, January 23, 2009 2:08 PM
To: PostGIS Development Discussion
Subject: [postgis-devel] Function Naming

I've placed my review in SVN here: docs/rfc/postgis_rfc_03_sheet.txt
You should be able to open it with any spreadsheet program that reads
tab-separated intput.
Please do a review in your abundant spare time.
Functions marked PUBLIC/KEEP should be part of the documentation.
Everything else should be invisible. We have a large collection of
functions that have been deprecated since 1.2. However, removing them
*will* break some client apps (mapserver, for example).
Hopefully the rest of it is self-explanatory.
P.
_______________________________________________
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.