On 10/6/07, David Cantrell <[EMAIL PROTECTED]> wrote:
> It wouldn't be the first time a module had had OS-specific features.  In
> this case, "if you're on Unix you can ...".

CPAN::Reporter already uses Win32::Process when it needs to honor CPAN
interactivity_timeout requests.  (Which I do plan to extend to test
timeouts, too.)

> to detect warnings*, but I suggest that anything sent to STDERR (which
> includes warnings) is Bad and should result in a WARNING email, because

No, no, no, no!

(a) to keep diagnostic output with tests in as close to the failing
test, we want to merge STDOUT and STDERR for reports

(b) plenty of modules test warnings by sending stuff to STDERR.
(Probably shouldn't but they do.)

David

Reply via email to