On Sun, Dec 01, 2002 at 10:12:43PM -0500, Chris Nandor wrote: > The perl test suite etc. doesn't need to care about the MacPerl app, only > the perl tool, but if you are looking to make modules installable via a > generic interface for MacPerl users, it should be able to work from the > MacPerl app, and without ToolServer, else it won't really help much, since > most users won't have ToolServer, let alone MPW.
This is for Module::Build's test target which uses Test::Harness which runs each perl test program in a seperate process. AFAIK there's just no way to do that on MacPerl without ToolServer and I can't think of another way to run tests. Except for a crazy idea. Write an AppleScript program which acts like Test::Harness. Have that run each perl program in turn and interpret the output. ./Build test then just calls that AppleScript program and quits (or the AppleScript quits any running MacPerl before trying to run the tests). Is it just stupid enough to work? -- Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/ Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One Follow me to certain death! http://www.unamerican.com/
