On 2008-08-13 22:13+0100 Andrew Ross wrote: > In principal I like the idea of being able to see the examples as they > are exectuted. I wonder whether the whole command line is necessary > though. Perhaps just echoing the example name would suffice and would > prevent too much unnecessary clutter in the output? For testing purposes > this is what is required. For a given test you know what the driver is > and what the output files will be.
Thanks for that feedback which has convinced me terse is better. I have therefore changed test_c.sh.in accordingly. I have also made a change there so the extra output you get in verbose mode occurs in the natural position before the execution of the command rather than afterward. As of revision 8644 I have used a similar style for all the other test*.in files except test_octave.sh.in which I made no changes to. > [...]Once we agree on a format I can add the necessary octave code. Thanks in advance. 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 __________________________ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
