Re: How To Merge Devel::Cover databases

[DrWhy]

After staring at Devel::Cover code for most of a day I believe the crux of the problem is that the cover program merges only half of the databases. It merges that runs portion which contains basic count statistics but does not merge the structure portion which contains mappings of counts data to source code locations. The solution is pretty straigthforward, a function to copy missing structure files from the various source databases into the structures directory for the target database.

It has nothing to do with a difference between the handling of .pm and .pl files.

I'm at least 75% sure this is right :)

[gcmandrake]

Dear Dr. Why and other denizens and seekers of Perl wisdom,

I have encountered a similar issue and need to merge Devel::Cover databases. Did you (or anyone else) make any progress on this issue? Thanks.

An unworthy Physicist posing as a Perl programmer,

gcmandrake

[DrWhy]

In fact I did solve that problem along with a couple of other issues I ran into along the way. I've been meaning to send diffs to the module's maintainer for inclusion in a future release, but it seems my big bag of round tuits has holes in it and the tuits keep leaking out.

Maybe this will give me the excuse I need to move this forward.

[gcmandrake]

In the spirit of the holidays (insert your favorite end-of-year holiday), please forward those diffs. It would be most appreciated and save us much mental anguish. (Not to forget that it would make us look good to our bosses.)
Thanks.
gcmandrake

[Anonymous Monk]

I did hack similar problem with few steps:
1. Check which of databases has the most files (let's say it is database3 in original example)
2. Put that database first in the command, i.e.

cover database3 database1 database2 ...

it seems to work for me - maybe will help somebody as well.