With the advent of intensive coverage tests and zealous Perl::Critic policies,
testing even simple things is getting messy.
even a moundain:
print 'hello' ;
triggers the wrath of InputOutput::RequireCheckedSyscalls with the
message "Return value of flagged function ignored".
This is
On Sat, Jan 05, 2008 at 12:53:35PM +0100, nadim khemir wrote:
> Next problem is coverage. Nothing upsets me more than a 99.8% coverage. I'd
> almost prefere a 80% coverage to 99.8%.
>
> So I tried to test that case with
>
> {
> use IO::File;
> my $current_fh = select ;
>
>
nadim khemir wrote:
> print 'hi' or carp q{can't print!} ;
I'm not even going to wade into the layers of neurosis demonstrated in this
post, but if you want to throw an error use croak().
--
...they shared one last kiss that left a bitter yet sweet taste in her
mouth--kind of like throwing up a
On Jan 4, 2008, at 7:09 AM, nadim khemir wrote:
I received an answer from Eric :
I wish I did have some kind of comparison. Here's what one user wrote
about choosing cabie:
http://www.golden-gryphon.com/blog/manoj/blog/2007/11/06/Continuous_Automated_Build_and_Integration_Environment.html
I
# from nadim khemir
# on Saturday 05 January 2008 03:53:
>print 'hello' ;
>
>triggers the wrath of InputOutput::RequireCheckedSyscalls with the
>message "Return value of flagged function ignored".
>
>...
>
>There is no chance that P::C could know I'm writting on a system
> handle that woul
On Jan 4, 2008, at 5:56 PM, James E Keenan wrote:
David Cantrell wrote:
On Tue, Jan 01, 2008 at 08:23:52PM -0500, James E Keenan wrote:
David Cantrell wrote:
If anyone can give me an idiots' guide to how to grab the most
recent
source tree, build it, and test it, then I can test it on the
Turns out the parrot build/test failed on SVN revision 24566, but
passed in revision 24567
So, I am gonna see if i can make a buildbot config to build and test
parrot, using an SVN polling configuration where I'll try and check
the SVN repo every N minutes and then do a checkout/build/test
On Saturday 05 January 2008 15.08.55 Michael G Schwern wrote:
> nadim khemir wrote:
> > print 'hi' or carp q{can't print!} ;
>
> I'm not even going to wade into the layers of neurosis demonstrated in this
> post, but if you want to throw an error use croak().
No more testing at 3 AM for me of cour
On Sat, Jan 05, 2008 at 11:00:41PM +0100, nadim khemir wrote:
> day an the answer was 'no'. Do you happend to know something about
> replacing 'print' with XS code short of patching perl (which doesn't sound
> like a good idea)
Not tested, but, can you
1: grab the address of print's op from PL
On Saturday 05 January 2008 20.21.59 Eric Wilhelm wrote:
> Even if it weren't a system handle, in what situation does print()
> return false?
>
> 1. Closed handle
> 2. Unopened handle
> 3. Disk full
>
> Unless I've missed one, you don't need to check the return value of
> print.
>
> I will
# from Matisse Enzer
# on Saturday 05 January 2008 13:25:
>Turns out the parrot build/test failed on SVN revision 24566, but
>passed in revision 24567
>
>So, I am gonna see if i can make a buildbot config to build and test
>parrot, using an SVN polling configuration where I'll try and check
# from Nicholas Clark
# on Saturday 05 January 2008 14:24:
>Not tested, but, can you
>
>1: grab the address of print's op from PL_ppaddr
>2: store it somewhere useful
>3: replace it in PL_ppaddr with your own function
That would be cool.
>Your own function calls the original, and then before ret
On Jan 5, 2008, at 4:20 PM, Eric Wilhelm wrote:
Is there any sort of build_ok/test_ok matrix for "$svn_rev x
$platform"
for parrot? Distributed, cross-platform projects tend to suffer
from "oh yeah, trunk is broken on $platform right now" (i.e. "as of 10
minutes ago"), which is hard to know
On Saturday 05 January 2008 14:00:41 nadim khemir wrote:
> Do you happend to know something about
> replacing 'print' with XS code short of patching perl (which doesn't sound
> like a good idea)
Sure, swap the pp_print function pointer in the opcode array before you
compile the code you wish to
I've set up a parrot buildmaster/slave, currently located at:
http://buildbot.eigenstate.net:8040/
---
Matisse Enzer <[EMAIL PROTECTED]>
http://www.matisse.net/ - http://www.eigenstate.net/
15 matches
Mail list logo
