On Tue, Aug 25, 2009 at 2:22 PM, Paul Larson<[email protected]> wrote: > Subrata Modak wrote: > >>> really just to "test the tests", would it make sense to put it under >>> /scratch or /testscripts as a separate script, rather than just include >>> it as yet-another-option for runltp? >> >> But, creating another script say under testscripts will be to duplicate >> again runltp code, as the same script should be able to parse all the >> options what we use with runltp. So, keeping it in runltp will just a >> little overhead. And, may be we can introduce some longoptions or >> manpage for ltp as suggested by people earlier !! > > It doesn't need to have anywhere near the same options available as > under runltp. Other than being able to specify a set of tests to run, I > can't really think of a need for many of the others.
Rather than make runltp into a huge long-options setup, why not separate out the common functionality in runltp into a library, make it source-able from runltp, runltp-lite, and whatever script is used to call valgrind? Thanks, -Garrett ------------------------------------------------------------------------------ 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 _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
