At YAPC::Europe there was some discussion about Test::Builder->level,
$Test::Builder::Level and the fact that they don't really work well as
implemented. I know we reached some sort of consensus about how to do it
better, but I've forgotten it.
Anyone remember?
--
Michael G. Schw
On Sun, 10 Nov 2002 23:10:40 +, Michael G Schwern wrote:
> At YAPC::Europe there was some discussion about Test::Builder->level,
> $Test::Builder::Level and the fact that they don't really work well as
> implemented. I know we reached some sort of consensus about how to do
On Sun, 10 Nov 2002, Michael G Schwern wrote:
> At YAPC::Europe there was some discussion about Test::Builder->level,
> $Test::Builder::Level and the fact that they don't really work well as
> implemented. I know we reached some sort of consensus about how to do it
> better
-BEGIN PGP SIGNED MESSAGE-
Moin,
On 11-Nov-02 chromatic carved into stone:
> On Sun, 10 Nov 2002 23:10:40 +, Michael G Schwern wrote:
>
>> At YAPC::Europe there was some discussion about Test::Builder->level,
>> $Test::Builder::Level and the fact that they don&
On Monday, November 11, 2002, at 04:10 am, Michael G Schwern wrote:
At YAPC::Europe there was some discussion about Test::Builder->level,
$Test::Builder::Level and the fact that they don't really work well as
implemented. I know we reached some sort of consensus about how to do it
bet
On Tue, Nov 12, 2002 at 04:21:38PM +, Adrian Howard wrote:
> >At YAPC::Europe there was some discussion about Test::Builder->level,
> >$Test::Builder::Level and the fact that they don't really work well as
> >implemented. I know we reached some sort of consensus ab
On Wednesday, November 13, 2002, at 08:37 pm, Michael G Schwern wrote:
On Tue, Nov 12, 2002 at 04:21:38PM +, Adrian Howard wrote:
At YAPC::Europe there was some discussion about Test::Builder->level,
$Test::Builder::Level and the fact that they don't really work well as
impleme
On Tue, Nov 12, 2002 at 04:21:38PM +, Adrian Howard wrote:
> Most of the time when I need to mess with level, the code that does
> the test is sitting in a different package from the one that is
> calling the test. How about having it walk up the call stack until it
> find a package that differ
