On Tue, 1 Nov 2005, Chris Dolan wrote:
Thanks for the feedback Mark and Sam. I chose Module::License::Report and posted my implementation to CPAN this afternoon.
Bravo and thanks.
Further feedback would be VERY welcome, as the module uses a few sketchy heuristics to guess at the license. To mitigate the uncertainty, I made it report a confidence number so the user can set a sketchiness threshold. The confidence is just a guess, but it's better than nothing. I'm thinking the next version should use multiple algorithms to guess the license and report higher confidence if they all agree.
That sounds even cooler. Perhaps a flag or a different function names could be used to get results as one license with one confidence value or multiple licenses per component with each having a seperate confidence. Each would have its place.
On a side note, I discovered that using Data::Dumper on my output object causes memory use to go through the roof. I think Data::Dumper is chasing into the CPANPLUS data structures and thrashing my machine. Is anyone familiar enough with CPANPLUS internals to know whether Data::Dumper problems are well known, or if I've stumbled on some new bug?
Data::Dumper is only good for looking at small chunks of stuff. Its very very very inefficient and there have been cases where Data::Dumper failed to produce something that could be eval'd back in once upon a time and eval'ing the result is inefficient too. Storable for the win here. Storable does everything Data::Dumper does poorly well and oopsy we don't care about presenting it visually. So use Storable for storing. Data::Dumper is just for glancing.
-- </chris> John Lundin once shaped the electrons thusly:
Ah. Okay, on the "nice to do" list. (Which in practice translates to "won't do unless it becomes inconvenient or is fixed upstream.")
