--count

[Andy Armstrong]

On 9 Aug 2008, at 13:43, Ovid wrote:
> I'm about to commit a change that allows one to pass a negatable  
> 'count' option to prove (it defaults to true).  This allows me to do  
> stuff like this:
>
>  prove --nocount t/aggregate.t

Cool ;)

> And my aggregate test runner handles the counting itself.  This is  
> similar to how counting is disabled when output is not going to the  
> terminal.  I notice as a side effect that the --nocount shaves 3 or  
> 4 wallclock seconds on the Test::Harness test suite :)

Wow. That sounds like an area for further investigation. I'm surprised  
terminal I/O is so costly.

> This adds a feature to prove, but does not alter current behavior.
>
> So my real question is, should I leave the versioning alone and let  
> and just let Andy handle that?  We're at 3.14 and I'm sooooooo  
> tempted to check this in as 3.141 :)


Any debate we have about that will tend to go round in circles...

I was planning to release 3.14 pretty soon - probably at YAPC. Also  
I'm wary of changing the number of digits after the decimal in version  
numbers; I'm never particularly confident that everyone's going to  
interpret them in the same way.

-- 
Andy Armstrong, Hexten