On Sat, Mar 19, 2011 at 06:33:39PM -0700, Alan Irwin wrote: > On 2011-03-17 20:09-0000 Andrew Ross wrote: > > > Please test this. User reports useful too. This is quite a change and > > a number of the old functions such as plcol still appeared dotted > > around the plplot code so I suspect users may be affected too. > > Wow! Thanks for all this extirpation and deprecation work! > > As of revision 11659 I have done some additional plcol > extirpation/replacement by plcol0, and dealt with some independent > bit-rot revealed by my preliminary tests. I have just completed 7 > comprehensive tests for the shared configuration type. These consist > of ctest, and 3 versions (build tree, installed examples tree and > traditional installed examples tree) of the test_noninteractive and > test_interactive targets. The results > show no obvious errors. > Furthermore, > > grep -v 'java/x' \ > ../comprehensive_test_disposeable/shared/output_tree/*.out |\ > grep -v problems | \ > grep -v WARNING | \ > grep -v 'x[0-9][0-9].java:' | \ > grep -i warning > > (where all the -v stanzas are to get rid of java warnings, cmake > WARNINGs, and PLplot run-time WARNING messages) show no build-time warnings > from > C/C++ compilers (a nice improvement!), and only gives this remaining stupid > octave run-time warnings: > > ../comprehensive_test_disposeable/shared/output_tree/ctest.out:6: > warning: split is obsolete and will be removed from a future version > of Octave; please use strsplit instead > > etc. I think changing split to strsplit in > plplot_test/test_octave.sh.in should fix this octave run-time issue, > but I don't understand the strsplit syntax for octave. Would you have > a go at that change, please, to remove this irritating warning?
I can do so easily. The reason I didn't is that strsplit was only introduced in octave 3.2 so doing so would require bumping our minimum octave version requirements for a relatively minor reason. Now octave 3.4 has been released though it might be the time for this change. > > Here is the current status of the languages that don't have a > perfect diff report: > > octave > Missing examples : 19 > Differing postscript output : > Missing stdout : > Differing stdout : > > Jerry has recently done all the hard pllegend, plstring, and plstring3 > API work so the remaining Ada examples 26, 27, and 33 issues should be > straightforward to fix for him, and similarly for Hez and OCaml > example 33. I am going to try to perfect lua in the next day or so > (except for example 19). So the difference issues should continue to > be reduced in the next little while. I am pleased with all this > progress toward what I hope is going to be a perfect diff report > for this release. Octave example 19 is now (finally!) implemented. Callbacks were easier than I anticipated. I just used a C wrapper for each callback function type. The approach is very similar to that used for Java. This might be a useful reference for lua if anyone fancies trying it. It is nice to finally have a clean diff report for octave. There is still some work to do here to implement the other callbacks, but the technically difficult bit has now been done. Andrew ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
