Thanks, Paul. As I get closer to the talk, I'll probably have you take a look
at my draft for more comments.
Jim Keenan
[1..39]),
'Current data count: 39')
"print_data_count() printed ideally");
I've Googled comp.lang.perl.misc and this list's
archive and have looked thru Perlmonks as well, but
haven't come up with a *simple* solution ('simple'
being de
on the HereToHelp page of
the Phalanx kwiki (http://phalanx.kwiki.org/index.cgi?HereToHelp) and
indicate what city or metro area you live in. Or hook up with one of
the local Perlmonger groups listed on the kwiki home page if you're in
one of those areas.
Jim Keenan
Leif Eriksen wrote:
I'd guess it is because you are seeing the output of the code after it
has been compiled-then-decompiled - it is compiled so it can run and
coverage statistics can be collected, then it is decompiled to relate
coverage stats to code lines. Now there are many ways to write cod
could site other
examples as well, but these suffice to illustrate the point.)
Now, I grant that these are merely displays, not live code.
Nonetheless, since the purpose of these HTML files is to guide a
programmer to lines of code whose test coverage needs improvement, I am
puzzled as to why the output in these two files differs.
Jim Keenan
lib/overload.pm
lib/re.pm
lib/strict.pm
lib/threads.pm
lib/threads/shared.pm
lib/vars.pm
lib/warnings.pm
lib/warnings/register.pm
My hunch is that these are modules and pragmas called
by Devel::Cover. Correct?
But why do I get these in the printout from
=~ s#::#/#g;
> $module .= '.pm';
> require $module;
> my ($path) = $module =~ /(.+)\//;
>
> mkpath($path,1);
> copy($INC{$module},$module);
> exec("$editor $module");
>
Jeff: Tried both
an tell, these are the tests in
t/Local.t which failed:
ok(sprintf('%x', timegm(gmtime(0x7fff))),
sprintf('%x', 0x7fff), # line 105
'0x7fff round trip through gmtime then
timegm');
ok(sprintf('%x', timelocal(localtime(0x7fff))),
sprintf(
On this page at the Phalanx web site
(http://qa.perl.org/phalanx/distros.html), it is
stated, "[the Phalanx 100] should NOT contain any
modules that are part of core Perl. Those will be
handled in a different phase of the project."
Can you elaborate as to how the core modules will be
handled?
jim
--- Paul Johnson <[EMAIL PROTECTED]> wrote:
> By the way, how big is enormous? I had never
> expected the size of the
> HTML output to be a problem, but it obviously is to
> some people.
'Enormous' is obviously a subjective judgment, so let
me describe the coverage files I've got and how I
wo
items
would be generated? Is this possible now? The
documentation for cover's options is, to say the
least, very terse, and I can't tell whether it can
DWIW.
So: Can Devel::Cover's 'cover' program be used to
generate reports of uncovered
statements/branches/conditions/only
[EMAIL PROTECTED] (Thomas Klausner) wrote in message
news:<[EMAIL PROTECTED]>...
> Hi!
> On Fri, Jul 23, 2004 at 08:41:58AM +0200, James
Mastros wrote:
>>> BTW, what's $report->{files}{ninja}?
> see here:
> http://use.perl.org/comments.pl?
Okay, I looked at that link, and the link to one of
12 matches
Mail list logo