Michael G Schwern wrote at Sun, 07 Jul 2002 04:06:02 +0200:
> You have to be extra careful about preserving the call stack, since the BLOCK is
>called inside
> warns_ok() as a subroutine. Consider:
>
> # line 5 "foo.pl"
> warns_ok { warn "Foo" } /^Foo in foo.pl at line 5$/;
>
On Monday, July 1, 2002, at 03:21 pm, Janek Schleicher wrote:
> Hello!
>
> On Sun, 30 Jun 2002, Adrian Howard wrote:
>
>> Nothing like it AFAIK - sounds useful. I've got places where I'm doing
>> this sort of thing, but I slurp up STDERR rather than wrapping
>> SIG{__WARN__} (which I assume is
On Thu, Jun 27, 2002 at 04:32:31PM +0200, Janek Schleicher wrote:
> I couldn't find a module doing this job on CPAN,
> so I'm ready to write a Test::Warn module.
>
> I thought that two methods should be implemented:
> warns_ok BLOCK REGEX, TEST_NAME (regex and test_name are optional)
> no_
On Thu, 27 Jun 2002 07:32:31 -0700, Janek Schleicher wrote:
> I couldn't find a module doing this job on CPAN, so I'm ready to write a
> Test::Warn module.
This is something I'd use.
> I'd like to know what you are thinking about ?, especially:
> - is it already on CPAN
> - Name: Test::Warn /
Hi!
Sometimes I want to test,
whether a module gives a (special) warning or not.
I couldn't find a module doing this job on CPAN,
so I'm ready to write a Test::Warn module.
I thought that two methods should be implemented:
warns_ok BLOCK REGEX, TEST_NAME (regex and test_name are optional
