he test system should be aware of the Perl
> version but be and independent product that produces a set of tests for
> Perl, t/ tests. This test system would be a general purpose tool and
> take Perl testing to a new level.
I agree, although I also still see a place for the t/*.t tests.
--
Paul Johnson - [EMAIL PROTECTED]
t
here. The API looks pretty well documented to me.
BEGIN { plan tests => 14, todo => [3,4] }
It's been there for a couple of years at least I think.
For the textual output, does it matter what it looks like? (Which is
neither an argument for or against changing it.)
--
Paul Johns
the number of tests anyway, and I think
you _should_ have to.
Of course, editing the todo list is a lot harder, but I wouldn't want to
go naming all my tests. Perhaps they could have an optional name?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
se our own parse tree or something. Hopefully that sort of thing
will be possible in Perl 6, if not sooner.
The other option is code instrumentation, but that requires parsing of
the code. Could be done I suppose, but I wouldn't really want to.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
f Perl 6 about being able to modify the
parse tree or byte code or something on the fly. That is really what's
wanted.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
(this morning) I'm afraid. There may well be
information by following Brent's links to gct. Be warned that many
similar techniques have different names though.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
either.
So there's a basic tutorial on code coverage, or at least my version of
it. Typing a few of these terms into google will probably provide a
basis for future research.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
27;. YMMV a lot, though.
I know it's religious, but since this is Perl for testing Perl, and will
be in the standard distribution (I suppose), we should probably stick as
close as possible to what's in man perlstyle.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
27;t want to just chuck it out. It must have scratched some
itch.
That's it. Basically, KISS. We really don't want bugs in the test
code. I'm willing to be told that I've oversimplified, but I'd like to
see real code that has to jump through hoops to cope with this
On Sat, Mar 17, 2001 at 01:19:02PM -1000, Tim Jenness wrote:
> On Sat, 17 Mar 2001, Paul Johnson wrote:
>
> > My motivation for this simple interface is that I see little benefit to
> > me as a module author in being able to write
> >
> > ok($x, 17);
> >
&
uck it on CPAN in a
while, pending any comments which are, of course, very welcome.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
display any of that info. If
> | you set $verbose = 1 you'll see all the test output. For failed tests
> | it will just report their numbers.
>
> Where do I set $verbose?
make test TEST_VERBOSE=1
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
:Bar.pm. I've run
some Gedcom.pm tests, and they seemed to give reasonable results (from
the point of view of being believable, rather than having good coverage.)
I'm happy to take it as a bug report if you'd like to send it to me.
There's some reasonably hairy code in ther
On Thu, Aug 09, 2001 at 10:27:04AM +0200, Arthur Bergman wrote:
> 01-08-09 01.50, skrev Paul Johnson på [EMAIL PROTECTED] följande:
>
> > This release fixes two problems:
> >
> > - Try harder to get the correct line number, even when perl has
> > optimised the line
;s even starting to get a little useful now
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
might like to write.
Available from CPAN soon, or now from my homepage.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
om my homepage.
Still lots to do though
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
with bleadperl.
I'll try to look further.
By the way, I got rid of perl-qa-metrics. It's basically dead, right?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
ests ended up in different directories and are not reported here.
- The URL is to my home machine so apologies if it is down or slow.
- I'll leave the data there for a while, but not for ever.
- This gives me plenty to work on
http://pjcj.sytes.net/cover.12493/cover_db/cov
On Sun, Oct 21, 2001 at 07:31:20PM +0200, Tels wrote:
> On 21-Oct-01 Paul Johnson tried to scribble about:
> > On Thu, Oct 18, 2001 at 10:42:33PM -0400, Michael G Schwern wrote:
> >> On Thu, Oct 18, 2001 at 12:07:26AM -0600, chromatic wrote:
> >> > > - Of those
w ;)
Indeed.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
o a CPAN mirror near you, or get it now from my home page.
This announcement brought to you by the ! key.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Sun, Oct 14, 2001 at 05:19:28PM +0200, Paul Johnson wrote:
> Hey! It's 0.12!
Better yet get 0.13. It's had some marginal quality control :-)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
rprised at just what constructs it did
include.
Maybe all the constructs it uses are tested earlier, but after all the
fingers that have been in the pie, it's probably time for someone to
take a good look at what gets tested where to make sure that the various
test programs do only use previously tested constructs as far as
possible.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
competitors ever see this code.
sub import { eval '$main::ONE--' }
1
one.plx
===
#!/usr/bin/perl
# Copyright Paul Johnson, 2002
# This program is mine. You can't have it.
# Program to print 1
BEGIN { $ONE = 2 } # Initialisation.
use ONE;# Abstracted aw
plied patches:
DEVEL14574
Built under linux
Compiled at Feb 9 2002 02:01:34
@INC:
/sw/packages/bleadperl/lib/5.7.2/i686-linux
/sw/packages/bleadperl/lib/5.7.2
/sw/packages/bleadperl/lib/site_perl/5.7.2/i686-linux
/sw/packages/bleadperl/lib/site_perl/5.7.2
/sw/packages/bleadperl/lib/site_perl/5.7.1/i686-linux
/sw/packages/bleadperl/lib/site_perl/5.7.1
/sw/packages/bleadperl/lib/site_perl
.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
keep my network
connection up long enough to get it on CPAN.
Enjoy,
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
ocally to
> each testfile, and that can be a problem if your testfiles chdir to
> different dirs.
Hopefully specifying -db,/full/path/to/db takes care of that.
Yes, this information should be in the docs.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
ease all ready to go. It might even
happen tonight if I can stay awake ...
I just want to test it a little ;-)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
> >
> > I just want to test it a little ;-)
>
> But, does it contain the B::SPECIAL fix? :)
Well, that bit of code has been completely reworked anyway. Do you have
a small example I could test with?
There are still bugs, but I think I should probably release it soon.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
should I
put them, and how should I get them there? Advice sought.
Remember, this is still alpha code, so don't expect too much and you
won't be too disappointed.
It's on my homepage if you can't wait for CPAN.
Enjoy.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Fri, Sep 06, 2002 at 04:40:40PM +0900, Tatsuhiko Miyagawa wrote:
> At Fri, 6 Sep 2002 01:59:36 +0200, Paul Johnson wrote:
>
> > Here's something really serious. As threatened, Devel::Cover 0.15 has
> > escaped into the wild, and is currently marauding around CPAN,
Just some bug fixes really. Oh, and the HTML output routine should be
able to find the templates now :-)
On CPAN and at my homepage, as usual.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
This release adds complete condition coverage, as long as I haven't
forgotten anything. New is coverage for xor, &&= and ||=. I also try
to be a bit more lenient about constructs such as $val = shift || "???"
Hmm. I suppose I'll have to add support for // now.
Us
l and working in the wee hours.
At least I didn't make two releases on the same day :-)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
t the same
address.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
ould failsafe. I don't know that I can
think of all the ways that one of my tests could fail to print the
expected output, so I prefer to explicitly state how many tests I am
going to run.
Though as Tels points out, this is probably not the biggest testing
problem facing most modules.
--
.
Is this the best way to handle this, or have I missed something?
In this case, Rafael fixed the bug and added passing tests, so there was
no problem, but in general what is the solution?
Now I've asked the same question three times I'll wait for enlightenment :-)
--
Paul Johnson - [
am not able to understand why is it showing the coverage as 0.
Neither am I. I went through exactly the same procedure, except with
bleadperl, and everything worked as expected. Did all of the tests
pass? Is this a 64bit perl? Has anyone ever run Devel::Cover with a 64
bit perl? Maybe it'
nstall/lib/site_perl/5.8.0
> /proj/dite/WorkArea/Raja/perl/install/lib/site_perl
>
> and
>
> program_1/cover.4 is :
>
> $db = {'collected' => ['statement','time'],'cover' => {'program_1.pl' =>
> {'statement' => {3 => [[[0]]]}}},'indent' => 0};
Looks about right for what you have reported.
Did you run make test on Devel::Cover? Did the tests pass?
Has anyone had any success with Devel::Cover on a 64 bit machine?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
That, I'm
working on.
http://pjcj.sytes.net/cover/cpancover/cpancover.html
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Mon, Dec 16, 2002 at 04:49:46PM +, Tony Bowden wrote:
> On Fri, Dec 13, 2002 at 12:16:53AM +0100, Paul Johnson wrote:
> > I also had thoughts along the lines of all tests not being equal.
> > Generally the earlier a test is run, the more important it is.
>
> This i
scripts tend to be run earlier in some setups, I'm not
> sure that's it going to be a useful distinction all of the time. There
> are certainly lots of test setups where it's not true for me.
Agreed.
It was really just a half baked idea of mine that may or may not have
any pr
; Test::More
> some of the recent stuff by Abigail
> Test::Harness
Feel free to take a peek at my cpancover project, which should give you a
(very) rough idea about the size of various modules and how well they are
tested.
http://pjcj.sytes.net/cover/cpancover/cpancover.html
--
rule
software is distributed with tests to be run at installation time, and if
the software is being installed in an environment where those tests cannot
easily be run, maybe just skipping them is an appropriate response.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
amon.
> Another question is:
> How can I see which statements and branches are covered and which not?
> Because currently I know that for example 80% are covered, but not which
> branches are not covered.
Have you run the "cover" program? That will give you a detailed textual
or html report.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
n.
If you are able to test against 5.8.0 or bleadperl, that would also be
helpful - otherwise I'll do that myself.
Thanks,
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
he best way to handle all Devel::Cover's tests now
failing.
I'd welcome any feedback and ideas for improvements.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
S.
My personal itch that this would scratch is to be able to specify
prerequisites if they can be easily satisfied, and just to output a
message if the installation is manual and the prerequisites are not
essential. (Yes, I know that doesn't make sense.)
--
Paul Johnson - [EMAIL PROT
ance it would be
> accepted,
The way I deal with this is to make a module that does all the heavy
lifting, give it an appropriate import sub, and then a test reduces to
something like:
use TestX ( opt1 => "x", opt2 => "y" )
That covers everything except the perl switches, but although I've never
needed that functionality, I suppose it could be quite important.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Sun, Jul 13, 2003 at 04:13:07PM +0100, Fergal Daly wrote:
> On Sunday 13 July 2003 15:53, Paul Johnson wrote:
> > The way I deal with this is to make a module that does all the heavy
> > lifting, give it an appropriate import sub, and then a test reduces to
> > something
fixes
- ... and many more
It should be on CPAN now, or get it from my homepage if you have a slow
mirror.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
self = shift;
> > $self->depends_on('build');
> > system qw( rm -rf cover_db );
>
> Not very portable :)
"cover -delete" would be the recommended way to do that. Portable, and
should still work when/if the database format changes.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
sed in the
latest release, and what isn't is on the TODO list.
> In the README:
>
> Requirements:
> - Perl 5.6.1 or 5.7.1.
> * May be 5.8.0|1 ? ;-)
> * Or 5.6.1 or greater ?
Actually, it was that way because 5.7.0 was not up to the job, and 5.8.0
didn't exist.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Tue, Sep 02, 2003 at 01:43:06PM +0200, Paul Johnson wrote:
> I've finally found no compelling reasons not to release Devel::Cover
> 0.21.
And hot on its heels comes 0.22.
This is a bugfix release. The first line of DESTROY blocks and overload
subs (and possibly some other thin
On Tue, Sep 02, 2003 at 11:17:00PM +0200, Paul Johnson wrote:
> On Tue, Sep 02, 2003 at 01:43:06PM +0200, Paul Johnson wrote:
>
> > I've finally found no compelling reasons not to release Devel::Cover
> > 0.21.
>
> And hot on its heels comes 0.22.
You wait for ag
d try
determining which of the coverage criteria is causing the problem,
though it may well be common to all the criteria. You could also try
putting an eval around the deparse calls at the end of get_cover() in
Devel::Cover.pm, though this will likely reduce the reported coverage
where the error has occurred.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
database when Devel::Cover is run, eg
perl -MDevel::Cover=-db,$PWD/cover_db ...
This particular problem seems to have hit the top of the most wanted
list so I'll see what I can do with it for the next release.
Who are these people who change directories and don't put things back
as they found them? ;-)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
Sure I need some hand holding on this.
Sounds like you're basically there to me.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
s to cpancover too. http://pjcj.sytes.net/cpancover/
Enjoy.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
27;ll
see what I can do on this front.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
Yes, you blinked and missed 0.25. I managed to put out a release that
didn't work with 5.6.1, except under the conditions with which I tested
it, so 0.25 came out rapidly to fix that.
This release adds a couple of other enhancements that were only half
implemented in 0.25.
--
Paul Jo
ce, having spent some time
last week trying to do just that. An easily automated task it is not.
However, if you can install the modules and run the tests on appropriate
systems I think running Devel::Cover should be almost trivial in
comparison :-)
The current state of the art is http://pjcj.sytes.net/cpancover/ which
is just the modules I could (reasonably) easily install and test on my
system.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
s down. I'm sure it wasn't
trivial.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
write separate databases, and see if any of
them are exceptionally large, then use the cover program to merge them.
Don't give up _just_ yet. I'd like to try to help you get some value
from Devel::Cover. But do remember, I've never called it anything other
than alpha.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
matically reduce my test suite.
> I'm looking for something that can raise a large flag and say - "Oi!
> This lot of tests over here seem to be doing almost exactly the same
> stuff as this stuff over here. Is that deliberate?"
Or maybe for a single test in the heuristics above substitute set of
tests.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Mon, Oct 20, 2003 at 09:34:38PM +0100, Tony Bowden wrote:
> On Mon, Oct 20, 2003 at 10:16:40PM +0200, Paul Johnson wrote:
> > I wrote "database" in quotes because currently we are talking about a
> > flat file, written using Data::Dumper and eval'd in. I hav
should all be
localised to Devel::Cover::DB.pm and, unless you change the internal
representation, the changes will be in the 33 lines of code which make
up the read() and write() methods. Of course, I'd expect that the
change will be increasing that number ;-)
--
Paul Johnson - [EM
t
necessary. Still, I may do something like that, if only because it helps
me during debugging.
I'm suffering from sleep deprivation at the moment, but I'll try this as
soon as I can.
Thanks again to all concerned.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
de being covered, of
course.
There is an overhead in the time needed to collect coverage, the memory
required whilst it is being collected, the disk space required to store
it, and the size of the (html) report files.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
ere gets passed in to the
report() method of the reporter module. None of the reports use that
feature at the moment, so it is just possible that things might not work
exactly as they should, but the infrastructure is in place.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
es out.
I have other patches waiting to be applied and other bug reports to
investigate, but I wanted to get this release out.
This release has been tested on 5.6.2-RC1 and 5.8.2 as well as more
mature platforms and bleadperl.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
58 2003
> +++ Html_subtle.pm Fri Oct 24 21:43:50 2003
Thanks very much.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
uggestions concerning this please followup here or
mail him directly.
There are some fairly significant changes in this release, so please let
me know if anything doesn't seem right.
Available from CPAN soon or my homepage now.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Mon, Dec 01, 2003 at 01:45:22AM +0100, Paul Johnson wrote:
People seem to be using this module. I keep getting bug reports, suggestions
and even patches ;-)
Changes in this release:
- Merge data from files with identical MD5 checksums (Arthur Bergman).
- Add do test.
- Handle $x
Nothing to see here, unless you use Windows, in which case this might
have a chance of working.
Bug reports welcome.
No, wait. I take that back.
Enjoy.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Mon, Dec 22, 2003 at 03:44:32AM +0100, Paul Johnson wrote:
> Nothing to see here, unless you use Windows, in which case this might
> have a chance of working.
And here's the version without debugging output. Bah!
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
Win32, but they are just rounding errors in
the percentages. I'll look at that later.
Enjoy,
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
the order they were created.
- Don't report multiple data from dynamically created subs.
- Add dynamic_subs test.
- Fix and document Devel::Cover::Op.
- Redo subroutine coverage so anon subs are covered correctly in 5.6.x.
Enjoy,
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Tue, Jan 13, 2004 at 10:22:52PM +0100, Paul Johnson wrote:
> This is a fairly important release because it fixes some errors in the
> coverage reported.
And introduces some others :-(
Hold off on this release - I'll upload a new one as soon as possible.
--
Paul Johnson - [EMAI
On Tue, Jan 13, 2004 at 10:39:02PM +0100, Paul Johnson wrote:
> On Tue, Jan 13, 2004 at 10:22:52PM +0100, Paul Johnson wrote:
>
> > This is a fairly important release because it fixes some errors in the
> > coverage reported.
>
> And introduces some others :-(
>
rmation should
allow these dependencies to be generated automatically, at least as far
as code dependencies are concerned, and would also allow more detailed
dependencies to be generated if required.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
non-existent platforms.
- Add DB option to make dump target.
Probably the most important change is that Devel::Cover will now work
with programs that turn on tainting. I gather this is important for
Phalanx. Hi Andy!
Available now from my homepage or from CPAN soon.
Enjoy,
--
Paul John
know whether the results look correct to you.
I'm not sure how we stand with threads.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
nding that supporting 5.6
is taking a lot of time that I would rather be spending on other things.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Fri, Apr 02, 2004 at 09:45:24PM -0500, Randy W. Sims wrote:
>
> Paul Johnson wrote:
> >I am considering dropping support for Perl 5.6 in Devel::Cover. Whilst
> >Devel::Cover basically works with Perl 5.6.1 and Perl 5.6.2, there are
> >many parts which are difficult or
fter using blib.
- Be silent if called via HARNESS_PERL_SWITCHES.
- Test against perl-5.8.4.
- Store cwd from when each module was required in order to find them again.
- Refactor and tidy XS code.
- Get cpancover running again with the DB changes.
- Normalise filenames.
--
Paul Johnson - [
missing
else). So one out of two, or 50% branch coverage. This fits in with
the statement coverage for the statements in the body of the if
statement being zero.
In order to get 100% branch coverage here you will need a test in which
$cx->[0] == 0 is true.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
Take appropriate shortcuts by examining the golden results in
test_output/cover/cond_or.* and using all_versions
- Try very hard not to mess up
I've not really expected anyone else to do this up to now. Medium term,
I'd like to improve this process, and I really want to find a way to run
Devel::Cover on itself.
Thanks again for the report.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
rt has shifted,
and so all the comparisons fail.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
re unwieldy, bring
standard software development techniques to bear. There is no reason
not to include modules in your distribution which are only required as
part of the test suite. Then again, I like Joshua Pritikin's
parenthetical question in Test.pm, "Your test code should be simpler
than
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
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
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
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
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
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
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
this fix in it, so let me
know if there are any other problems.
--
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
1 - 100 of 299 matches
Mail list logo
