Michael G Schwern listed:
[...]
warnings::register (almost no docs)
There are no tests for warnings.pm either.
Note that there are two distinct points here :
1. test the warnings issued by the perl interpreter; this is done by
lib/warnings.t, that calls the various files in
On 2001.09.19 17:37 Paul Marquess wrote:
Nope, it does both. The test files that start with digits are intended to
test the features of the warnings pragma itself along with it's interaction
with $^W. All the other files test specific warnings.
The tests for warnings::enabled and
On 2002.01.05 23:45 Michael G Schwern wrote:
Here's an interesting alternative. Do Clocal $^C = 0 just before
running the tests, though that's pretty ugly.
Interesting idiom, but I don't see when this can be done.
But I rwally like the environment variable better, because with the
On 2002.01.13 22:25 Michael G Schwern wrote:
Why would this:
BEGIN {
push @INC, 'foo';
}
put 'foo' into @INC twice if it were compiled? The compiled program
should not be storing the post-BEGIN value of @INC, it should store
the original value at startup.
The
On 2002.01.14 22:27 Michael G Schwern wrote:
B::Deparse has slowly gotten very good at figuring out BEGIN blocks
from 'use' statements and putting them in the right places. Hard
fought knowledge. Steal from it.
There are still problems with pragmas. (As I was working on B::Deparse
the last
Andy Lester wrote in perl-qa :
I can do this:
use PHP::Session 0.10;
to ensure a version number, but I can't do this:
use_ok( 'PHP::Session', '0.10' );
The optional args to use_ok are for imports, not for version numbers.
[...]
Before I go digging into a patch, is this
Tels wrote in perl.qa :
--- Cover.pm.old Wed Sep 4 23:36:14 2002
+++ Cover.pm Wed Sep 4 23:38:46 2002
-144,6 +144,8 sub report
for my $sub (Todo)
{
+next unless $sub-[1]-CV-isa('B::CV');
That's a guard against a B::SPECIAL object, isn't it ?
Well, B::SPECIAL
Tels wrote in perl.qa :
Well, B::SPECIAL is for one of the internal constants '0', '1' and
'undef'. There ought to be a better interface to this, but I can't
really figure out what to improve.
I have no idea what you talk about - I am a total B:: newbie :)
The big story :
Each time a
Mark Fowler [EMAIL PROTECTED] wrote:
I'd like to have a custom version of is(), say binary_is(), that
reports 'strings 1 and 2 differ at byte 635, got 0x92, expected 0x42'
or 'strings 1 differ in length, got 3874, expected 3875'.
Oooh, that would be really helpful. I often find myself
