I have now (revision 11540) restored the default build by disabling plcolorbar everywhere but C and OCaml. Example 33 in C currently does not plot the plcolorbar pages unless the user specifies the -colorbar option. This means all test diffs for example 33 are against the C version without the plcolorbar pages being plotted.
Here are the current diff test results as generated by the test_diff_psc target in the build tree: c++ Missing examples : Differing postscript output : Missing stdout : Differing stdout : f77 Missing examples : 33 Differing postscript output : 27 Missing stdout : Differing stdout : f95 Missing examples : 33 Differing postscript output : 04 18 26 27 Missing stdout : Differing stdout : java Missing examples : Differing postscript output : Missing stdout : Differing stdout : octave Missing examples : 19 Differing postscript output : Missing stdout : Differing stdout : python Missing examples : Differing postscript output : Missing stdout : Differing stdout : tcl Missing examples : 33 Differing postscript output : 04 18 26 27 Missing stdout : Differing stdout : ada Missing examples : 33 Differing postscript output : 04 18 26 27 Missing stdout : Differing stdout : adathick Missing examples : 33 Differing postscript output : 04 18 26 27 Missing stdout : Differing stdout : lua Missing examples : 33 Differing postscript output : 04 18 19 26 27 Missing stdout : Differing stdout : d Missing examples : 33 Differing postscript output : 04 18 26 27 Missing stdout : Differing stdout : Since plcolorbar is not part of this comparison, most of these remaining differences are due to pllegend not being propagated to one of the languages. I suggest now is an excellent time to do the pllegend propagation without interference from plcolorbar in example 33. Simply follow the part of examples/c/x33c.c that has nothing to do with plcolorbar, and you should be okay. Note, some have expressed concern about how to propagate the char** text and symbol strings in pllegend, but those arguments follow very closely how the legline strings in example 17 are passed to plstripc. So propagating pllegend to your favorite language should be quite straightforward. Meanwhile, Hez and I will be working on plcolorbar, and that will likely involve further API changes for it. Once, we are both satisfied with it for C (and OCaml), I plan to show examples to the list for further discussion to make sure it fits everybody's needs (as far as we know at this time). Even then, experience tells me that further API changes will probably become necessary as we gain more experience with plcolorbar so I think we should mark that API as experimental for this release cycle and wait to propagate it to all language bindings and the various language versions of example 33 to the next release cycle. 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); PLplot scientific plotting software package (plplot.org); 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 __________________________ ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
