On 2009-09-11 08:54+0200 Arjen Markus wrote: > By the way: I have the same failure wrt example 19 (snprintf is not > defined) as David Aldrich.
Hi Arjen: I have given this a new subject. First, I would like to discuss a possible technical solution for this issue, then the implications with regard to our platform testing. I. Possible technical solution Since you have a fairly up-to-date Windows platform, I guess this means snprintf is unequivocally not available on any "bare" Windows platform. I don't know the situation for Cygwin and MinGW. Hez, Andrew: is replacing snprintf with sprintf (just as in all other examples) what should be done? Or would you like to do something more general here like configuring plcdemos.h to take advantage of the CMake variables, PL_HAVE_SNPRINTF and _PL_HAVE_SNPRINTF to implement essentially the same solution as in plplotP.h? II. Platform testing implications I am afraid this result means at least the bare Windows platforms did not get tested with ctest since August 5th, the last time example 19 was changed. That lack of testing during the last month before our release of 5.9.5 could have had pretty serious implications for that release, but I believe we got off fairly lightly this time (assuming that once we straighten out the issue, the rest of the examples do work on bare Windows). The problem with attempting to deal with this Windows testing issue in future is there are many bare Windows platforms as well as Cygwin and MinGW (with and without MSYS) to test. So our three active developers with access to Windows are unlikely to have time, disk space, and Windows compiler licenses to test all variations. To help deal with this issue for all future releases let's do some specific coordination of which developers will take firm responsibility for running at least ctest on the Windows platforms that are accessible to them. That coordination will probably reveal some Windows platforms that won't be tested, but it would be good to identify those. In any case, I think we should formally ask for some testing help on the plplot-general list a week before each release from now on for all platforms but especially for the Windows platforms where we don't have good testing coverage. (A week should give us time to deal with most issues that come up). From our download statistics and number of questions asked on plplot-general there appears to be more and more interest in PLplot so encouraging the new users to help out with testing on all our platforms (especially for the many different Windows platforms where our developer coverage is thin) makes a lot of sense. If there is general consensus this is a good idea, and Hazen is willing to send such an e-mail the week before each release, I will put a reminder in README.Release_Manager_Cookbook. 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 __________________________ ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
