On Sun, Apr 17, 2011 at 10:15 AM, Andrea Aime <[email protected]> wrote: > So this means we now have function overloading, but not the java way, based > on attribute types, but on the argument names instead? > That sounds odd to me, wouldn't it be better to leave overloading aside and > just > demand a unique name?
Which also makes me wonder about describing not only the names, but also the types of the arguments. Ins't that just as important documentation wise? Here is the function reference I wrote some time ago for geoserver: http://docs.geoserver.org/stable/en/user/filter/function_reference.html For each function we have a name, arguments and their types, and a function description. Btw, also detailing the process funtion wrapper, they all have variable size arguments, and each argument is a Map<String, Object>... not sure how they fit with this proposal Cheers Andrea -- ------------------------------------------------------- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 mob: +39 333 8128928 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------- ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
