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
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
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
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
[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
[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
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
--- 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
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
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(
=~ s#::#/#g;
> $module .= '.pm';
> require $module;
> my ($path) = $module =~ /(.+)\//;
>
> mkpath($path,1);
> copy($INC{$module},$module);
> exec("$editor $module");
>
Jeff: Tried both
additional light on this in the last six
>weeks?
>
No. So it's still on my TODO list. Thanks for looking into it.
Jim Keenan
>From: Will Coleda via RT <[EMAIL PROTECTED]>
>Date: 2007/07/02 Mon AM 08:28:11 CDT
>To: [EMAIL PROTECTED]
>Subject: [perl #43463] [BUG] Parrot Bug Summary "Requestors with most open
>tickets" doesn't DWIM
>Need to strip out the HTML comment on the link; the url for
>you is actually:
>
>http://r
One of the test files I wrote for configuration step class auto::alignptrs,
t/configure/124-auto_alignptrs-05.t, has been getting failure reports on one
particular test -- but not on all platforms, and not on a platform I have
access to.
I would like to follow up with the folks running these sm
A wiki has been created for the Perl Hackathon in Chicago coming up Fri-Sun
Dec 14-16 -- just a little over two weeks away.
http://perlcast.com/hackchicago2007/index.cgi
Are any Parrot developers besides my planning to attend? If so, please
register and sign up on the wiki.
Thank you very mu
Todd Olson via RT <[EMAIL PROTECTED]> on 2007/11/28 Wed AM 08:39:24 CST wrote:
>
>One feature I have been exploiting extensively in my Perl 5 installs
>is cpan.pm's MyConfig.pm which permits me to overlay Perl's %Config
>and to swap sets of config changes in and out with out messing with
>the ba
>From: Andy Dougherty via RT
>Date: 2007/12/11 Tue AM 08:38:17 CST
>Subject: Re: [perl #48459] [PATCH]: Refactor config/inter/progs.pm into 2
>config steps
>
>I don't think this will work. Specifically, to conduct a "basic test of
>that compiler's functioning" you need to compile *and link*
I'll try this out on Darwin and (Debian) Linux this weekend and see what
happens. Thanks.
>From: Will Coleda <[EMAIL PROTECTED]>
>
>I am confused why this wasn't failing for allison & chromatic. I added
>in the missing headers in r26227.
>
I'll try to update and give it another spin later today.
>From: Will Coleda <[EMAIL PROTECTED]>
>
>
>I am confused why this wasn't failing for allison & chromatic. I added
>in the missing headers in r26227.
>
Note that I was reporting on an earlier revision. In
"20080304.26216.pdd17pmc.txt", the second bunch of digits is the revision
number at which
>From: Will Coleda <[EMAIL PROTECTED]>
>I am confused why this wasn't failing for allison & chromatic. I added
>in the missing headers in r26227.
>
All tests passed at r26228 (except the macro.t test that's been failing in
trunk).
kid51
>From: "[EMAIL PROTECTED] via RT" <[EMAIL PROTECTED]>
>Date: 2008/03/26 Wed PM 05:13:17 CDT
>To: [EMAIL PROTECTED]
>Subject: Re: [perl #52130] [BUG] postconfigure tests hanging on feather.
>> > I'll try to look into this. What's puzzling is that we get tested on
>>> *many* Linux boxes but the o
22 matches
Mail list logo