Would it be a helpful indication to be able to have perl report the upper
memmory bound on exit? Or better, the memory used: upper- minus lower bound
Then we can enable this in the smokes and have the test suite add the usages
of the individual tests and show it in the summary line:
u=3.86 s=1.
On Thursday, August 29, 2002, at 05:29 PM, Michael G Schwern wrote:
> There's already the beginnings of something like this in
> t/TestInit.pm, but
> it wasn't updated for the PERL_CORE trick. Nor do I know if it can be
> entirely trusted.
>
> Also, Nick's example is a little odd. You usually
On Thu, Aug 29, 2002 at 06:23:26PM +1000, Ken Williams wrote:
> I admit that I was a little surprised to see 'lib' stuff here
> and not 'blib' stuff. Don't blibs get created when building
> modules in the core?
Everything winds up in lib/ before the tests are run. All non-XS modules
are never
On Thu, Aug 29, 2002 at 12:29:58AM -0700, Michael G Schwern wrote:
> Also, Nick's example is a little odd. You usually don't want '.' (ie. t/)
> in your @INC. It's more like this:
>
> BEGIN {
> if($ENV{PERL_CORE}) {
> chdir 't';
> @INC = '../lib';
> }
>
On Wed, Aug 28, 2002 at 09:32:10PM -0700, chromatic wrote:
> Perhaps we are looking at this from the wrong direction. Instead of
> installing bundled modules, perhaps a shell should be able to specify that
> certain dependencies are available only for testing. That way, users
> wouldn't neces
There's already the beginnings of something like this in t/TestInit.pm, but
it wasn't updated for the PERL_CORE trick. Nor do I know if it can be
entirely trusted.
Also, Nick's example is a little odd. You usually don't want '.' (ie. t/)
in your @INC. It's more like this:
BEGIN {
