Hi all,
I've been banging my head for quite a while on a bad file descriptor problem.
Basically, I have TAPx::Parser 0.12
(http://users.easystreet.com/ovid/downloads/TAPx-Parser-0.12.tar.gz) in
development and I have tried to clean up the 'tprove' script by adding
TAPx::Parser::Source::Perl.
- Original Message
From: Ovid [EMAIL PROTECTED]
sub get_stream {
my ( $self ) = @_;
my $command = $self-_get_command;
local *FH;
# -| is safer, but not portable.
if ( open FH, $command | ) {
return TAPx::Parser::Iterator-new(\*FH);
}
Hi all,
You can dowload the next version at
http://users.easystreet.com/ovid/downloads/TAPx-Parser-0.12.tar.gz or wait for
it to hit the CPAN.
To see the test colors, try this:
perl -Ilib examples/tprove_color2 --verbose examples/t/*.t
Changes:
- Added a test colorization script
* Ovid [EMAIL PROTECTED] [2006-07-30T06:19:17]
After struggling with this for over an hour, I think I finally found the
problem. If I *don't* localize the filehandle, this problem goes away.
Apparently, localizing that typeglob caused the underlying descriptor to
disappear once the localized
chromatic wrote:
produce a short, focused manuscript
This sounds remarkably like a series of technical books the began
being published in Massachusetts, in the late 70's or early eighties
- I think they were called the berry-sized handbooks or the nuts
sell handbooks, something like
I'm confused. We have a heirarchy, not a web: CPAN signs author keys,
authors sign modules.
Wouldn't x509 certificates (SSLish) be better suited for this?
--
Ian Langworth
