# from Eric Wilhelm
# on Sunday 08 April 2007 09:41 pm:
>Alternatively, maybe what I want is just for Pod::Coverage to not
> check any symbols that aren't static subs in the package in question.
> (I guess that would solve the whole @INC bug as well and we could
> just statically scan the code.)
Hi all,
The only easter egg I got today was this conundrum:
Pod::Coverage reports aliased methods as undocumented because
Method::Alias does the eval("package $your_package; sub $alias
{shift->$canonical([EMAIL PROTECTED])}") thing.
Of course, it doesn't bother reporting things like accessors
On 8 Apr 2007, at 22:41, Fergal Daly wrote:
Yes I did. If you want your structured (or any) diagnostics to be
associated correctly and you want to allow forking you have to tag
each line with test numbers. If forking is deemed not important then
tagging them is not necessary.
But for the severa
On 08/04/07, Andy Armstrong <[EMAIL PROTECTED]> wrote:
On 8 Apr 2007, at 12:46, Fergal Daly wrote:
> Prepending something to every line is necessary if you want perfect
> multiplexing.
But we don't want that to be part of TAP do we? What's with the
insistence that TAP has to be responsible for m
On 8 Apr 2007, at 12:46, Fergal Daly wrote:
Prepending something to every line is necessary if you want perfect
multiplexing.
But we don't want that to be part of TAP do we? What's with the
insistence that TAP has to be responsible for multiplexing?
Or we could just go with a proposal that
On 08/04/07, Andy Armstrong <[EMAIL PROTECTED]> wrote:
On 8 Apr 2007, at 02:07, Fergal Daly wrote:
>> begin
>> begin
>> ok
>> end
>> begin
>> not ok
>> end
>> end
>
> Yes, I said it was nestable but my point is that it once you start
> nesting you can no longer have the demuxer separate from the
