[postgis-tickets] [PostGIS] #2529: LWGEOM API for read-only PointArrays is not enforced

[PostGIS]

#2529: LWGEOM API for read-only PointArrays is not enforced
---------------------------------+------------------------------------------
  Reporter:  marcelosoaressouza  |       Owner:  pramsey                                
      Type:  defect              |      Status:  reopened                               
  Priority:  medium              |   Milestone:  PostGIS 2.2.0                          
 Component:  postgis             |     Version:  trunk                                  
Resolution:                      |    Keywords:  ST_FlipCoordinates, PostGIS, PostgreSQL
---------------------------------+------------------------------------------

Comment(by pramsey):

 For practical purposes, though, we have a situation where we are *usually*
 taking a copy at the start anyways. Clarifying the liblwgeom API and
 making the read/write guards actually have effect would be beneficial in
 general. Do we have actual performance use cases where having, for
 example, lwgeom_transform() always return a fresh geometry, be an
 insupportable performance penalty? worth not having a clearer API
 (enforced by const!)

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2529#comment:12>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.