[postgis-devel] [PostGIS] #1212: [raster]: st_intersects signature change - documentation out of synch
PostGIS
trac at osgeo.org
Wed Sep 28 05:10:10 PDT 2011
#1212: [raster]: st_intersects signature change - documentation out of synch
----------------------------+-----------------------------------------------
Reporter: robe | Owner: pracine
Type: defect | Status: new
Priority: medium | Milestone: PostGIS 2.0.0
Component: postgis raster | Version: trunk
Keywords: |
----------------------------+-----------------------------------------------
Comment(by robe):
Pierre should have the final word on this. Just my 2c.
I just think the number of variants you have is getting out of hand. It's
worse when you have two functions that take exactly the same arguments but
in different order. Too prone for ambiguous name references or when
things accidentally get auto cast.
The only thing going for raster,int,raster,int is that it follows the
pattern of other functions (rast and then band). The downside of it is
that if someone just wanted to
to rast, rast -- then they would have to input all args. This is why I
preferred
rast1,rast2,int1,int2
over rast1, int1, rast2, int2
the number of permutations of these while may make some things shorter to
type I think will just cause to confuse new users and old users and become
a great burden to maintain as you'd have to think of all cases where
things may be thrown in the wrong slot.
I know Pierre loves overloading because it gives users the freedom to not
remember the order of things and arbitrarily leave things out willy nilly,
I just think it adds too much management burden and scares users off when
they see a function with 12 overloads.
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1212#comment:6>
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.
More information about the postgis-devel
mailing list