On 2014-11-09 09:39-0800 Alan W. Irwin wrote:

> 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.

Hi Phil:

Following your commit f40deb1 to change the names used for the plmap*
arguments for C and C++ to more explanatory names, I have followed up
with commit a69ef1d for doing the same with the swig-generated
bindings.

@Everybody:

Phil's plmap* argument name changes and my corresponding changes
caused no regressions (as expected) for the propagation effort whose
status remains the same, i.e., the problem bindings/examples continue
to be

f95
   Missing examples            :
   Differing postscript output :  08 19
   Missing stdout              :
   Differing stdout            : 
tcl
   Missing examples            :
   Differing postscript output :  08 19
   Missing stdout              :
   Differing stdout            : 
ada
   Missing examples            :
   Differing postscript output :  08 19
   Missing stdout              :
   Differing stdout            : 
adathick
   Missing examples            :
   Differing postscript output :  08 19
   Missing stdout              :
   Differing stdout            : 
ocaml
   Missing examples            :
   Differing postscript output :  08 16 19 33
   Missing stdout              :
   Differing stdout            : 
d
   Missing examples            :
   Differing postscript output :  08 19
   Missing stdout              :
   Differing stdout            :

>From contacts I have had both on and off list, I am glad to report
Arjen has promised to deal with Fortran and Tcl (eventually, after our
current collaboration to upgrade the Fortran bindings in general is
completed), Jerry has promised
to deal with Ada, and Andrew has promised to deal with D for this
forthcoming release.

Assuming you all come through, that should only leave OCaml as a
concern for this forthcoming release.

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
__________________________

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to