Hi,
My Runops-Movie depends on Imager with it's png feature. I'm not sure
exactly how to accomplish this as a dependency. My module can depend
on Imager but I have no way to communicate to the running CPAN harness
that the Imager that's been delivered isn't sufficient.
Right now the only abort
On Tue, Dec 22, 2009 at 2:23 PM, Michael G Schwern schw...@pobox.com wrote:
Joshua ben Jore wrote:
The just-released EU::MM 6.56 repeats this pattern frequently:
open my($fh), '', ...
or croak(Can't open ... for writing: $!);
...
print $fh ...; # no error checking
On Tue, Dec 22, 2009 at 4:29 PM, Michael G Schwern schw...@pobox.com wrote:
A little experimentation with a small disk image shows that close() will
error if there's no disk left. No need to check every print. And a close()
You have to check every print. Most prints will just extend the
On Tue, Dec 22, 2009 at 4:29 PM, Michael G Schwern schw...@pobox.com wrote:
A little experimentation with a small disk image shows that close() will
error if there's no disk left. No need to check every print. And a close()
wrapper is trivial. It does mean there needs to be a close() for
On Tue, Dec 22, 2009 at 9:29 PM, Marvin Humphrey mar...@rectangular.com wrote:
On Tue, Dec 22, 2009 at 09:03:42PM -0800, Joshua ben Jore wrote:
On Tue, Dec 22, 2009 at 4:29 PM, Michael G Schwern schw...@pobox.com wrote:
A little experimentation with a small disk image shows that close
The CPAN smokers regularly spit back UNKNOWN results where the text of
the error is:
Output from '/usr/bin/make':
make: *** No targets specified and no makefile found. Stop.
One example is
http://www.nntp.perl.org/group/perl.cpan.testers/2009/07/msg4616138.html
but there are many,
On 9/20/07, demerphq [EMAIL PROTECTED] wrote:
The solution is to add a dummy line to f() to make sure that it mentions $x.
{
my $x = 'A';
sub f { my $y=$x; sub { print \$x; $x++ } }
sub g { sub { print \$x; $x++ } if $x }
}
My experience was just a void context
On 9/14/07, Paul Johnson [EMAIL PROTECTED] wrote:
I've started on a sort report to provide an optimal test ordering, so
that you can do the majority of your testing as soon as possible, or
identify tests which don't add to your coverage, but this isn't finished
yet.
That's interesting. How do
On 9/12/07, James E Keenan [EMAIL PROTECTED] wrote:
I have had a proposal accepted to do a presentation at the Pittsburgh
Perl Workshop (Oct 13-14) on Better Code via Coverage Analysis during
Testing (http://pghpw.org/ppw2007/talk/725).
During this presentation I hope to:
1. Channel pjcj
On 7/31/07, David Golden [EMAIL PROTECTED] wrote:
On 7/31/07, chromatic [EMAIL PROTECTED] wrote:
Please explain to me, in detail sufficient for a three year old, precisely
how:
1) POD can possibly behave any differently on my machine versus anyone
else's
machine, being non-executed
On 6/29/07, A. Pagaltzis [EMAIL PROTECTED] wrote:
* Joshua ben Jore [EMAIL PROTECTED] [2007-06-29 05:35]:
I had a terrible and powerful idea just now. Use Runops::Trace
When all you have^W^W^W you newly discover the hammer…
That's it exactly. I've got this neat tool. What can I use it to do
On 6/28/07, David Golden [EMAIL PROTECTED] wrote:
On 6/28/07, Eric Wilhelm [EMAIL PROTECTED] wrote:
I was thinking there needs to be a shared filehandle with a stream of
time on it similar to the below, but with various time() and sleep()
methods overridden. Calls to time() or sleep() would
On 6/19/07, chromatic [EMAIL PROTECTED] wrote:
On Tuesday 19 June 2007 14:06:05 Joshua ben Jore wrote:
It's on CPAN with the original name. I just stole the namespace. I
don't think chromatic will mind.
It can even support the API described in Perl Hacks if or when it gets
a custom import
On 6/7/07, Eric Wilhelm [EMAIL PROTECTED] wrote:
I've never seen the benefit of pod after __END__. IMO, your code and
docs should follow the same order/groupings. That, and you have to
It has two benefits. Separating code from pod prevents it from being
wholely unreadable without syntax
On 4/17/07, Ovid [EMAIL PROTECTED] wrote:
Posted at http://www.perlmonks.org/?node_id=610484
So I have some code I'm testing which relies on a class with a whole
bunch of niggling, annoying little methods getting called hither and
yon. For the purposes of my tests, however, I really only care
On 3/2/07, Michael G Schwern [EMAIL PROTECTED] wrote:
Eirik Berg Hanssen wrote:
Michael G Schwern [EMAIL PROTECTED] writes:
chromatic wrote:
On Thursday 01 March 2007 17:46, Adam Kennedy wrote:
Actually, isn't UNIVERSAL::can($x, 'can') still valid? I seem to
remember that at one point it
On 2/25/07, Joshua ben Jore [EMAIL PROTECTED] wrote:
I've hated it how ref() does the wrong thing so frequently so I wrote
a fix for it. I like to use mock objects to feed fake or proxy objects
to other things but this breaks when things not under my control use
ref() to examine the class
On 2/27/07, A. Pagaltzis [EMAIL PROTECTED] wrote:
Owh goodness aragh *twitch*
Together with the contortions required to safely examine $@ after
an eval I'm getting tempted to put Unbreak::Eval on the CPAN.
Please do. Did David Golden ever send his $@ examining snippet to you?
It did
On 2/27/07, Joshua ben Jore [EMAIL PROTECTED] wrote:
On 2/27/07, A. Pagaltzis [EMAIL PROTECTED] wrote:
Owh goodness aragh *twitch*
Together with the contortions required to safely examine $@ after
an eval I'm getting tempted to put Unbreak::Eval on the CPAN.
Please do. Did David
On 2/26/07, Michael G Schwern [EMAIL PROTECTED] wrote:
Joshua ben Jore wrote:
On 2/25/07, Yuval Kogman [EMAIL PROTECTED] wrote:
Is there a function that is to this as overload::StrVal is to
stringification?
Wouldn't that just be CORE::ref $obj ?
No. I don't know how to solve this problem
On 2/26/07, Yuval Kogman [EMAIL PROTECTED] wrote:
On Sun, Feb 25, 2007 at 23:22:13 -0800, Joshua ben Jore wrote:
Ick Neither ref nor blessed have never been a booleans before and
even this doesn't change that. Ref couldn't even used to decide if you
had an object because the two false
I've hated it how ref() does the wrong thing so frequently so I wrote
a fix for it. I like to use mock objects to feed fake or proxy objects
to other things but this breaks when things not under my control use
ref() to examine the class of an object.
No longer. Under most circumstances ref()
On 2/25/07, Yuval Kogman [EMAIL PROTECTED] wrote:
Is there a function that is to this as overload::StrVal is to
stringification?
No. blessed() doesn't lie to you and I don't change that. I didn't
provide any ref-alike that provide the complete old behavior.
If you read t/basic.t file, you'll
On 2/25/07, Yuval Kogman [EMAIL PROTECTED] wrote:
On Sun, Feb 25, 2007 at 22:51:43 -0800, Joshua ben Jore wrote:
On 2/25/07, Yuval Kogman [EMAIL PROTECTED] wrote:
Is there a function that is to this as overload::StrVal is to
stringification?
No. blessed() doesn't lie to you and I don't
of the bytecode, but they exist.
On a recent JRE I can even figure out the rough size of the stack
frame using a trick to get to a very limited piece of access to
the pointers.
Ben
On 2/1/07, Adrian Howard [EMAIL PROTECTED] wrote:
On 1 Feb 2007, at 16:28, Joshua ben Jore wrote:
[snip]
There's is nothing special about what T::E is doing to detect errors -
it just turns out the popular practice of looking at $@ is flawed.
That's a problem with the pattern and I expect
On 1/31/07, Adrian Howard [EMAIL PROTECTED] wrote:
On 30 Jan 2007, at 20:11, Joshua ben Jore wrote:
Interestingly, this has caused me to wonder how well Test::Exception
handles the corner cases where $@ is clobbered during the scope ending
of eval{} and related.
It doesn't. It's been on my
On 1/30/07, A. Pagaltzis [EMAIL PROTECTED] wrote:
* Pete Krawczyk [EMAIL PROTECTED] [2007-01-30 19:00]:
How about code that dies with an object? dies_ok lets you
inspect the object in $@, whereas throws_ok only lets you see
if it's part of a class. What if you want to see if $@ meets
On 1/30/07, Nadim Khemir [EMAIL PROTECTED] wrote:
I believe the example in Test::Exception is not as good as it could be.
# Check that something did not die
lives_ok { $foo-method2 } 'expecting to live';
Doesn't explain much about when to use it.
You'd use (lives|dies|throws)_ok when
On 1/30/07, David Golden [EMAIL PROTECTED] wrote:
On 1/30/07, Joshua ben Jore [EMAIL PROTECTED] wrote:
Interestingly, this has caused me to wonder how well Test::Exception
handles the corner cases where $@ is clobbered during the scope ending
of eval{} and related. I've just filed a bug
On 1/24/07, Nik Clayton [EMAIL PROTECTED] wrote:
Has anyone ever used Test::More and Fatal together?
I have a test script, where each test builds upon the work of the previous
step (it's part of the Subversion Perl bindings test suite, and it checks
out files, makes changes to them, commits
On 1/9/07, David E. Wheeler [EMAIL PROTECTED] wrote:
On Jan 9, 2007, at 3:05 AM, Adam Kennedy wrote:
Just some tips I thought I'd pimp... ewr... I mean pass on.
Obviously, you should call it `pimp` rather than `pip`. Probably
isn't used by any other program in the universe, either. ;-)
I
On 1/4/07, jerry gay [EMAIL PROTECTED] wrote:
On 1/4/07, Andy Lester [EMAIL PROTECTED] wrote:
On Jan 4, 2007, at 11:21 PM, Eric Wilhelm wrote:
No. You either have tests that are ordered, or you don't.
Stated as if it were some sort of immutable law of the universe!
It is as far as
On 12/17/06, Nadim Khemir [EMAIL PROTECTED] wrote:
I will also have a bunch of tests that need to be run under the debugger. I
will use Devel::ebug as it is the only way to control the debugger. There are
tests in the ebug distribution that I might be able to copy but I would also
like to try
On 9/29/06, Alexandr Ciornii [EMAIL PROTECTED] wrote:
Hello!
For a long time I'm using Test::Reporter. Now I participate in Vanilla
Perl project (http://win32.perl.org). I've started CPAN smoke.
I've come to several ideas regarding cpantesters. I want your opinion on
them.
1. YAML files on
at it, and look
at the results. If the results are good I then put an md5 hash of the
image into a regression test.
Strawman.
A graphing library is an obvious example where functional testing should be
used prior to automated regression testing.
Ben
is probably written in the wrong language.
I suppose you could consider a source filter, but I couldn't recommend
that.
I'd make a slightly stronger statement than that: If you were congenitally
insane, wilfully stupid or drunk, you could consider a source filter for this.
Ben
fix it for running such an archaic Perl. People should be encouraged
to move to a more modern environment whenever possible.
Ben
not that I think Agile methods don't
work, but for a methodology that has so much to say about project Scope, I
think some discussion of the scope of applicability of the methods might
be worthwhile.
Ben
39 matches
Mail list logo
