ere is a TPF presence in GSoC and/or
GCI next year, please raise your hand, jump around, shout and, above
all, start doing whatever is necessary to make that happen.
--
Paul Johnson - p...@pjcj.net
http://www.pjcj.net
in the last 18 months) and has the advantage of already
existing. I'm not convinced that Perl6 needs a list separate to Perl5.
--
Paul Johnson - p...@pjcj.net
http://www.pjcj.net
uture
release."
OK - strictly speaking that's talking about intervening nested
aggregates.
--
Paul Johnson - p...@pjcj.net
http://www.pjcj.net
at probably explains a
lot too.
In any case, the patch looks fairly minimal - you might be able to
retrofit it to Perl1 without too much trouble.
But I'd go the virtual machine route too, all else being equal.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
equivalent would break in Perl 5, where the "objects" can change internal
> private state as a side effect of being read. For example, conversions are
> cached.
Which is where, in C++, you would be using the mutable keyword. I don't
think this has yet made it into any C stan
get is known as coretest in Perl 5.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
27;s food available
if you are hungry enough.
> Hence, I'm resolving the ticket.
Sorry if this opens it up again.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
Devel::Cover has sometimes uncovered
questionable constructs that have otherwise gone unnoticed, but my first
thoughts would be that it was a bug in Devel::Cover.
Has anyone managed to shine any additional light on this in the last six
weeks?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
uot;make cover" target, the Perl world
seems to have settled on "make testcover".
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
stant rather than a constant pointer.
> =head2 Mixing C
>
> Combining Cs on a pointer and its constants can get confusing.
Very much so. s/constants/contents/ I suspect? Or maybe s/its constants/what
it points to/ ?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
me patches for Devel::Cover::DB::validate_db and
Devel::Cover::DB::is_valid to do something more than just check that one
file exists there ;-) (Those methods should probably be merged too.)
(And sorry they are not already written. I suspect something a little
more robust there might have saved you a bit of pain.)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
uot;received" or whatever, and I end up having
to look at the output a lot closer than I think I should in order to get
things the right way around.
But perhaps it's just my brain that's wired backwards.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
corrupted.
How are you killing the process? Are you sending it SIGKILL (9) for
example? Maybe you could send it something a little nicer which might
allow to process to clean up.
Devel::Cover does its work in the very last END block. You really need
to let it run to completion.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
statements, branches and conditions in
the file, and other similar data.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
e a great problem. So I am interested in what problems this
causes down the line. To stop the warning I suggest the following
options:
1. Fix Devel::Cover. Go on, please. You know you want to ;-)
2. Hack the source to disable the warning.
3. Filter the output.
4. Pretend you didn't see it.
Most people take the fourth option since it really shouldn't cause any
further problems.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
in
> it, please advice if my understanding and approach is
> right or not.
If this works then that's fine. You can probably be a bit more specific
with 'no warnings "recursion"', but as I say, it is only a warning. I
should sort it out in the Devel::Cover code itself at some point.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
ge databases. The reason is that the database is
read into a perl data structure. (The "database" is really little more
than a Storable dump of a Devel::Cover::DB object.) I'm afraid that the
pragmatic approach its probably to throw RAM at the hardware.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
vel/Cover/DB/Structure.pm line 269
> =
I think so. Perhaps nothing was written to the database at all?
$ perl -MStorable -e 'retrieve "/dev/null"'
Magic number checking on storable file failed at ../../lib/Storable.pm
(autosplit into ../../lib/auto/Storable/_retrieve.al) line 331, at -e
line 1
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
eed to come back with a bit more
information.
Good luck.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
d add after "use
> Devel::Cover" to make it works as
> "-MDevel::Cover=+ignore,\\.pt$ ...".
I think that "use Devel::Cover qw( +ignore .pt$ );" should do that.
See -M in perldoc perlrun.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
file ($db, $file, $options);
print_branches ($db, $file, $options) if $options->{show}{branch};
print_conditions ($db, $file, $options) if $options->{show}{condition};
print_subroutines($db, $file, $options) if $options->{show}{subroutine};
}
}
>From h
general it is much better to ignore modules whilst gathering
coverage. This has the added bonuses of making the whole thing
quicker, using less space, and mostly working.
So something like perl -MDevel::Cover=+ignore,\\.pt$ ... might be what
you are really looking for.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
eed,
http://www.copyright.gov/circs/circ03.html only talks about:
The symbol © (the letter C in a circle), or the word “Copyright,” or
the abbreviation “Copr.”
I wouldn't have said anything, but your correction seems to indicate
that the (C) is important. Is my information outdated?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
; %foo {'bar'} >> DTRT, but I can't
> remember it", which certianly happens to me fairly often.
Well, I'd obviously quite like that ;-)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Thu, May 04, 2006 at 01:56:44PM +0300, Markus Laire wrote:
> On 5/1/06, Paul Johnson <[EMAIL PROTECTED]> wrote:
>
> >But then again, as I said, I really don't see the problem that is being
> >solved.
>
> This "long-dot" can be used for many thin
CHED */ to shut up lint, writing
if ((a = b)) to shut up gcc, and even adding # uncoverable to keep
Devel::Cover quiet ;-)
[ No, that last one doesn't work yet. ]
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
_.foo for @things_to_foo;
or something.
I like lining up my code as much as the next programmer, and probably a
lot more, but I just don't see the need for this syntax which seems
ugly, confusing and unnecessary.
But then again, as I said, I really don't see the problem that i
On Mon, Apr 10, 2006 at 10:26:14AM -0700, Dan Fabulich wrote:
> Paul Johnson wrote:
>
> Re: CPAN...
> >I don't see a problem with that sort of thing going on CPAN, at least
> >not from that point of view, but I do wonder if it is worthwhile given
> >that it will
n assist with?
As far as strategy is concerned, I think this is the right way to go. I
don't see any point in rewriting the Java code if it is doing everything
necessary (I discovered I needed a fairly recent (or possibly just not
ancient) version of java to get it to work), and being consistent with
solution
such as the one you noted, where the call is conditional on some
constant which can be set to false allowing the optimiser to remove the
whole thing from the op tree.
I suppose you could consider a source filter, but I couldn't recommend
that.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
ble to do that, and maybe
to declare which hash keys or array elements are valid.
Do we have that already?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
to give combined coverage for the script
and any modules used.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
son in the quality of the test
output. The only downside is that it is another configuration on which
I need to test before making a release.
Oh, and Test::JSON works well for me. Thanks!
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Fri, Nov 04, 2005 at 11:02:42AM -0500, Will Coleda wrote:
> The mail list strips out .t attachments (Robert? is this necessary?)
This was changed on perl5-porters a few weeks ago, and since then I
don't recall seeming a marked increase in troff spam.
--
Paul Johnson - [EMAIL PROTECT
ns.
I may yet completely overhaul the option handling. That this is a
possibility is the major reason I still call the code alpha.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Fri, May 13, 2005 at 05:18:40PM +0100, Tim Bunce wrote:
> On Fri, May 13, 2005 at 10:51:56AM +0200, Paul Johnson wrote:
> > On Fri, May 13, 2005 at 03:00:39PM +1000, [EMAIL PROTECTED] wrote:
> >
> > > [EMAIL PROTECTED] wrote:
> > >
> > > >Cov
est basing your work on cpancover in the Devel::Cover
distribution. (I think I have mentioned this before.)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
g small, self contained test
cases, go a long way to helping such problems get solved ;-)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
he slides are at
http://www.pjcj.net/yapc/yapc-eu-2005-dc-advanced/slides/
and the more basic stuff can be found off http://www.pjcj.net/yapc/
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
is big enough - 512M might still be enough. See
http://www.perladvent.org/2004/5th/
Do the same when you need to upgrade something.
I managed to install svk and a bunch of other stuff in this fashion
without problem.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
n my local configuration.
>
> The Test::Builder::Tester distribution includes
> Test::Builder::Tester::Color. That might be useful - or might serve as a
> good basis to build something on.
See also Apache::Test.
http://perl.apache.org/docs/general/testing/testing.html#Colored_Trace_Mode
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Mon, Jul 11, 2005 at 02:54:19PM -0700, Michael G Schwern wrote:
> On Mon, Jul 11, 2005 at 11:22:51PM +0200, Paul Johnson wrote:
> > > my $foo = $bar || default(); # DC ignore X|0
> > >
> > > "Hey, Devel::Cover! Ignore the case where the right side of thi
nd even tests inline, which tells me that I
really should be ignoring their opinions, but I try to please my users
anyway, and so I'll see what I can do.
> Ignored conditions would be green, but perhaps a slightly different shade of
> green so they can be spotted if you're lookin
On Wed, Jul 06, 2005 at 01:36:10AM +0200, Abigail wrote:
> On Mon, Jul 04, 2005 at 05:21:01PM +0200, Paul Johnson wrote:
> >
> > Unfortunately, upgrading isn't always an option. Anyone can type
> >
> > $ ./Configure -des && make && make test in
usands of machines in dozens of different
configurations function at least as well as they did before is a little
harder.
And whilst I know how to manage all this, sometimes it's hard enough
just stopping people from mandating the use of ksh, Java and XML.
Having said all that, feel free to do what you want with 5.004 support.
I don't care! I have 5.005!
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
d only be for the
benefit of people and modules that mess with the op tree. Again, I
submit that an optimisation that changes normal behaviour is broken and
that, in general, programmers shouldn't need to worry about what
optimisations are going on under the covers.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
hanges are between 5.8.0 and 5.8.1, but I notice the docs
are wrong there. They wont be in the next release.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
ck there at all, so that suggests something
> funny is going on.
Certainly. Of course, it's always possible and quite likely that there
is a bug in my code somewhere. But there is also a chance that I am
conflating two ops, since I have yet to come up with a way to uniquely
identify an op (suggestions welcome). You're not running on 5.6.x are
you?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
at the moment, I'm afraid.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Fri, May 13, 2005 at 03:00:39PM +1000, [EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] wrote:
>
> >Covering the XS portion of the code with gcov is possible, and Devel::Cover
> >will create all kinds of nice webpages and statistics for you too.
> >Paul Johnson
create a "total coverage" out of four
> different types of coverage stats.
That total is calulated as the sum of all the covered constructs over
the sum of all constructs. That figure has more dubious value as it
assumes that all coverage criteria are equal when we all know that some
cri
eased
if you were able to add a "stop after the very first test that fails
because that's the one I'm going to fix now" option while you're looking
at this.
Or even at some other time. Or somebody else. I'm not that fussy
really.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Thu, Apr 28, 2005 at 02:44:30PM +0100, Adrian Howard wrote:
> On 28 Apr 2005, at 14:23, Paul Johnson wrote:
>
> >Using Test::More, I would like to send some diagnostics to be seen only
> >when the harness is running in verbose mode.
> [snip]
>
> diag "s
Using Test::More, I would like to send some diagnostics to be seen only
when the harness is running in verbose mode.
There doesn't seem to be a way of doing this. The best I could come up
with is:
sub vdiag { pass("@_") }
but this has little to recommend it.
Thoughts?
-
t since then it would seem that for
some strange reason more people have been exposed to functional
programming.
http://www.mail-archive.com/perl6-language@perl.org/msg11967.html
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
ogram Perl
as if it had sequence points and undefined behaviour. This often
results in explaining what they are, but maybe that's not such a great
problem.
See http://www.eskimo.com/~scs/C-faq/faq.html, especially sections 3.8
and 11.33 for details.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
est script tweek-then-foo.t which tweeks the system and then ensures
> that foo.t still passes. How do I write tweek-then-foo.t?
I would do it in the same way as if this had nothing to do with tests.
That is, abstract away the common code into a module, which can also
live under t/
--
Paul Jo
On Fri, Apr 01, 2005 at 01:47:36PM -0600, Walter Goulet wrote:
> Finally, I wanted to confirm an assumption: I can split test.pl into a
> set of seperate t/*.t test scripts regardless of whether I'm using
> Test or Test::More.
Yes. Or neither or both.
--
Paul Johnson - [EMAIL P
o determine the value of an arbitrary boolean expression
I can probably go into nauseating detail on any of these points if
required.
If you've got this far, thanks for listening!
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
gy behind the module - I'll just install it and run it.
This argument can also be applied to (most of) the modules in the Tie
namespace, though I know that not everyone is of the same opinion in
this regard.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
to that which ran gcov2perl?
Other than that, I'm not sure what to suggest. If you can send me
enough to reproduce the problem I'd be glad to look into it.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Mon, Mar 07, 2005 at 10:33:11PM +, Nicholas Clark wrote:
> On Mon, Mar 07, 2005 at 07:59:40PM +0100, Paul Johnson wrote:
>
> > To do it properly it would need to be on a machine somewhere which would
> > accept uploaded coverage databases from anyone who wanted to subm
=> 't/emulate.t',
>'1110216226.25105.54436' => {
> 'run' => 't/01_use.t',
>'1110216262.25141.01103' => {
> 'run' => 't/twoObjects.t',
>'1110216265.25143.07361'
ngs posted on cpan.org right next to the usual
> >>test results?
> >
> >It still chokes on certain not uncommon constructs like threads.
> >
> On that note, is forking also problematic?
Forking should be fine, for certain definitions of fine.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
.module, TOPs);
NDEB(D(L, "require %s\n", SvPV_nolen(MY_CXT.module)));
break;
}
Thanks for the report and sorry for the delay fixing it, and that you
needed to provide a workaround.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
. Unfortunately, this
also has the effect you have noticed. B::Deparse has options to control
how the output is displayed, but I wasn't able to find anything that
improved on the current output in the general case.
I suppose that's the price you pay for TIMTOWTDI.
[ Is that a Python prog
ting_here)
I've checked that in to my development copy along with a test case based
on your failing example (I removed the rand part). If things are OK for
you I'll release a new version with this fix soon.
Thanks for the minimal test case. Bug fixes are so much easier with a
concise way to r
the quoting and
attributions. s/le/wle/ gives the hint too.
Mike is quite right of course. And the code which handles this is one
of the more simple parts of perl5. Provided you're not too worried
about what's going on under the macros, I suppose.
if (SvTRUE(left) != SvTRUE(right))
RETSETYES;
else
RETSETNO;
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
tain that there's not another version of Storable
around which could be being picked up? Maybe you could try printing out
the version of Storable being used before nstore is called?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
get a coverage report about it. Which is normally fine,
since you don't want one anyway, and even if you did you couldn't
because Devel::Cover uses Storable internally.
Whether this is related to your main problem I can't tell, though I have
have seen that warning plenty of times before but never encountered your
main problem.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
he regex engine and trying to do this, but to be
> honest I don't really see it happening for me. So, I figure the next
> best thing is to throw this idea out here and see if anyone else runs
> with it.
Micheal suggested mjd's Rx might be useful. Jeff Pinyan's
Re
rning a status or dying or
something. Or do it via OO. Or whatever.
Doing something similar before the test is run seems useful too.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
tters."
>
> I'd like to be able to s/Python/Perl 6/ above, but after many discussions on
> this topic, I'm still not sure if I can.
http://www.nntp.perl.org/group/perl.perl6.language/9576
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
Boags.
It's a long way to come for a drink, but I appreciate the offer :-)
> Leif Eriksen
> aka Mr Testing SmartyPants (you can tell I'm please with myself cant you)
I hope the effort proves worthwhile.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
Windows but not on Darwin?
Normally they would not be covered by default, being core modules. Is
it possible that your perl is in a different location from that with
which the ppm was created?
When Devel::Cover runs it will tell you which directories are being
ignored by default. See the documentation to alter this if it is wrong
for you. (Or manually hack Devel::Cover::Inc, but that's not a
supported solution.)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Sat, Nov 13, 2004 at 12:33:01PM +1100, Leif Eriksen wrote:
> First, thanx so very much for responding so quickly...
That was just to make up for the short delay here, and the much longer
delay to your last mail to me ;-)
> Paul Johnson wrote:
>
> >On Sat, Nov 13, 2004 at 1
bug in this area which first appeared in
perl-5.8.3. Which version are you using? Still redhat's dodgy 5.8.0?
http://www.nntp.perl.org/group/perl.perl5.porters/85930?show_headers=0
(I meant use_ok in that message, not isa_ok.)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
he code in question is in Cover::report(),
the section that starts "if (exists &B::check_av)". In a standard 5.8.0
that would be false. In 5.8.1 and, it would seem, RH9 5.8.0 it is true.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
e or directory at
> /temp/din/Devel-Cover-0.47/cover line 101
> Can't open database
>
>
> Any clue why this error occurs.
Ah yes - that option was new in 0.48. I suggest you either upgrade to
version 0.49, use -ignore with the full path to File::Copy, or live with
getting the
k with, so thank you very much for that. Actually, a
small test case is probably the single biggest help to me in cases such
as this. The only thing better is if it is accompanied by a perfect
patch ;-) I will see if I can work out some sort of solution for the
next release.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Fri, Oct 08, 2004 at 04:50:28PM +0530, Padubidri Nagaraja Rao, Guruprasad
(Guruprasad)** CTR ** wrote:
> Hi,
>
> I've few perl scripts called from C++ programs. I wanted to do code coverage
> for
> those scripts and i am using Devel::Cover module. Since the existing C++
> programs are huge a
On Tue, Oct 05, 2004 at 11:32:23AM -0700, David Wheeler wrote:
> On Oct 5, 2004, at 11:25 AM, Paul Johnson wrote:
>
> >I wonder whether we shouldn't try to standardise the target name before
> >it's too late to do so. Module::Build uses covertest, I've always
ly. (Yes, I'm that
lazy. I even have make aliased to n.)
So, standardise on covertest? Opinions?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
I'm
aware of a few conditions where some coverage is not reported correctly.
If anyone hits that and can reduce it to a small script I'd be very
grateful.
I have a bit of a backlog of mail that's been waiting for me to get this
release out. If you've sent me something I
o collect more coverage
make clean # as expected
And I even get coverage on the Perl parts of the conf files, which was a
pleasant surprise ;-)
[ Just before sending this I notice Geoff has recommended something
better, but I'll send this too as another WTDI. ]
#!/usr/bin/perl
# Cop
a problem, but it obviously is to some people. The
current output is much smaller than that from the report that I
originally wrote. I don't think there's much scope for reducing its
size without also reducing the content.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
people will
be able to upload coverage databases which will then get merged and
reports produced. I'm slowly making the changes to Devel::Cover to
allow that.
When such a system is in place, it could be queried in order to provide
some input towards the kwalitee.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
ome of those will be a lot harder than others, and the metrics will
obviously need to be weighted, but I just wanted to throw out a few
thoughts from the safety of the peanut gallery.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
used to fail because the tests took
too long to run, though I see it passes now. And my Shell::Source
module has passed, even though it doesn't run on Windows ;-)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
n that line (0 for first)
5. which part of the coverage (based on the internal representation)
6. reason
Michael Carman is looking at making this more usable. Columns one and
five are especially problematic at the moment. So for the time being
you might prefer to simply note which parts cannot be covered and why,
and later convert that to whatever system we ultimately use.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
the limit.
But I suppose I'll turn off the warning from Devel::Cover. That seems
the most pragmatic solution at the moment.
In the meantime, please just ignore the noise. Or maybe add -X to your
command line, if you're feeling brave.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
f he wants to do
> > anything about it.
>
> I suppose I could do that, but it seems kinda strange to ask him to change
> stuff around just so we can have good test metrics. but, per your
> suggestion, at least there is a simple workaround - thanks for that.
Yes, though you coul
this fix in it, so let me
know if there are any other problems.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
s one - it will need to
be fed to the author of Parse::Yapp and he can decide if he wants to do
anything about it.
In any case, the first fix will be in the next release, and thanks again
for the great test cases.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
hen you go calling them in a program it gets upset. The
solution is to only override the subs for as long as is necessary. The
change is in my development copy and will be in the next release.
Thanks again for reporting the problem and producing a small test case.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
Foo.pm is not an option.
>
> I have some ideas outlined below, but I'd like to get your recommendation.
[snip]
> In general I'd like to get your opinion on how to mock unsuccessful
> require.
local *CORE::GLOBAL::require = sub { die "require $_[0] failed&quo
y the best way, as Devel::Cover will try to collect as
little information as it can while the tests are running.
If you have already collected the coverage the -file and -exclude
options to cover will allow you to choose the files on which to report.
I should probably change those to be -select
otherwise I know of a number of larger modules
which also exhibit this problem.
Thanks for reading this far. I must stop now as half time is over, so
it's back to the football ...
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
not particularly attached to any one name, but I would like to
ensure consistency, so now seems like the right time to pick a good
target and stick to it.
I'd be interested in any opinions on this.
And then, at some point, add a similar rule to MakeMaker?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
build path on Windows (Max Maischein).
- Allow Devel::Cover to be used under mod_perl (Philippe M. Chiasson).
- Handle $x ||= 1 and friends nicely, including subs and *foo{THING}.
Enjoy,
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
1 - 100 of 216 matches
Mail list logo
