The argument naming convention was part of jody's last proposal on adding
arguments names to functionName. In some cases I tried to be a bit smarter in
geoserver and as a workaround handle some "well known" argument names such as
"geometry". For example:
>
>
>
I had a similar idea; if we could handle "geom", "geom1","geom2","geomN" (and
also "int","int1","int2","int3","intN") - even if just for the gt-main based
functions a lot of of boiler plate code would not be needed (and it would
encourage consistency).
For the most part when I added names to functions I was consistent; so I think
this approach would take us 90% of the way.
Jody
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
