On Tue, Mar 28, 2006 at 09:47:54AM +0100 Fergal Daly wrote: > A far simpler solution (that I've posted before recently) is to > output test "numbers" like > > .1.1 > .1.2 > .1.3 > .2.1 > .2.2 > .1.4 > > etc where the first number signifies the thread/process and the second > is just an increasing sequence within that thread. The . is there at > the start so that Test::Harness doesn't get upset. > > Interprocess comms using Storable seems like overkill and sounds like > the sort of thing that would have "fun" bugs,
I really don't care how it is done, as long as it is eventually done at all. :-) As I can see it, there now exist at least two propositions on how to fix this problem. The ones responsible for Test::More/Test::Harness should take any of these proposed solutions and put them in. I just would like to be able to write test-scripts that fork without these annoying and ugly counter-mismatch messages. For that I sent one possible solution which ends my responsibilities in this matter. :-) Cheers, Tassilo -- use bigint; $n=71423350343770280161397026330337371139054411854220053437565440; $m=-8,;;$_=$n&(0xff)<<$m,,$_>>=$m,,print+chr,,while(($m+=8)<=200);
