On 2014-11-09 11:08-0000 phil rosenberg wrote: > HiI am just writing the documentation for the new map API. I wonder if some > of the variable names are now misleading. For example type can either be one > of the plplot built in map types or the filename of a shapefile, so perhaps > name or file might be better. Perhaps more importantly in a shapefile the > coordinates may not be lat/lon (this is true for the ones used in the new > example) so the variables minlong etc are misleading, they should perhaps be > minx etc instead. > I realize however that people have been implementing the new functions in > other bindings so this would have been better flagged a few weeks ago, so I'm > sorry if this generates extra unnecessary work. Should we change them or > leave them the same?
Hi Phil: I am all for explanatory argument names. So please go ahead and choose what you think are the best plmap* argument names for C, C++, and the DocBook documentation. I will take responsibility for making the corresponding changes in the 4 languages I have dealt with. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
