On 2014-01-23 09:57+0800 Hailiang Wang wrote: > Hi Alan, > > Here are results from revision 12954: > > c_plbtime is not documented. > c_plconfigtime is not documented. > c_plctime is not documented. > c_plgcmap1_range is not documented. > c_plgdrawmode is not documented. > c_plot3dcl is not documented. > c_plscmap1_range is not documented. > c_plsdrawmode is not documented. > c_plsurf3dl is not documented. > number 0 parameter name mismatch for function plprec ( set setp ) > number 0 parameter name mismatch for function plpsty ( n patt ) > number 0 parameter name mismatch for function plptex3 ( x wx ) > number 1 parameter name mismatch for function plptex3 ( y wy ) > number 2 parameter name mismatch for function plptex3 ( z wz ) > number 2 parameter name mismatch for function plscmap1l ( pos intensity ) > number 2 parameter name mismatch for function plscmap1la ( pos intensity ) > number 6 parameter name mismatch for function plscmap1la ( coord4 a ) > number 0 parameter name mismatch for function plseed ( seed s ) > number 4 parameter name mismatch for function plshade ( xmin left ) > number 5 parameter name mismatch for function plshade ( xmax right ) > number 6 parameter name mismatch for function plshade ( ymin bottom ) > number 7 parameter name mismatch for function plshade ( ymax top ) > number 4 parameter name mismatch for function plshade1 ( xmin left ) > number 5 parameter name mismatch for function plshade1 ( xmax right ) > number 6 parameter name mismatch for function plshade1 ( ymin bottom ) > number 7 parameter name mismatch for function plshade1 ( ymax top ) > parameter count mismatch for function plspal1
Hi Hǎiliàng: Thanks for your further report. Since all of these argument name mismatches are new (and later in the alphabetized list of functions than the previous name mismatches that I solved), and this report and your previou report also ended with a count mismatch, it appears that your check logic stops all processing if there is a parameter count mismatch. Could you change that logic to stop processing for that particular function but continue further checking additional functions for argument count and argument name mismatches? The reason I have requested this logic change is I would prefer to see all mismatches in one report rather than piecemeal depending on what count misatches I have solved previously. 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 __________________________ ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
