On Sat, Feb 17, 2001 at 09:46:31PM -0500, [EMAIL PROTECTED] wrote: > Why is t/TEST anything more than a thin wrapper around Test::Harness? Because of potential fragility. If Perl isn't entirely together when you're running the tests, the last thing you want to do is load up Test::Harness. t/TEST is (supposedly) crafted in such a way that it avoids using things that are likely to be broken. -- The complex-type shall be a simple-type. ISO 10206:1991 (Extended Pascal)
- Why t/TEST and not Test::Harness? schwern
- Re: Why t/TEST and not Test::Harness? schwern
- Re: Why t/TEST and not Test::Harness? schwern
- Re: Why t/TEST and not Test::Harness? Simon Cozens
- Re: Why t/TEST and not Test::Harness? schwern
- Re: Why t/TEST and not Test::Harness? nick
- Re: Why t/TEST and not Test::Harness? schwern
- Re: Why t/TEST and not Test::Harness? Jarkko Hietaniemi
- Re: Why t/TEST and not Test::Harness? Jarkko Hietaniemi
- Re: Why t/TEST and not Test::Harness? schwern
- Re: Why t/TEST and not Test::Harness? Andy Dougherty
- Re: Why t/TEST and not Test::Harness? Andreas J. Koenig
- Re: Why t/TEST and not Test::Harness? Jarkko Hietaniemi
- Re: Why t/TEST and not Test::Harness? Philip Newton