On Sep 28, 2006, at 11:11 AM, John Peacock wrote:
Ken Williams wrote:
Probably the first step is to add a failing test case to t/
moduleinfo.t, would that be fairly easy?
I have to rewrite a custom reporting app for work, so I'm not going
to get to it before tonight. It's fairly straightforward:
1) create a dummy module with the offending two lines;
2) include the path where #1 is located into the @INC paths;
3) call Module::Build::ModuleInfo::new_from_file with the
appropriate parameters in an eval and check to see if any warnings
are thrown.
Looks like it's even easier since there's a lot of infrastructure
already in place for these tests. I've checked in a failing test.
-Ken
