On Thu, Oct 16, 2003 at 11:12:53AM -0700, chromatic wrote:
> On Thu, 2003-10-16 at 10:46, Ovid wrote:
>
> > I was browsing through the Perl core tests and I saw that some tests in the t/uni/
> > directory used
> > Test::More, but most other tests would explicitly 'print "ok 1\n"'.
> >
> > Is thi
Chromatic wrote in perl.qa :
>
> Stuff in t/op mostly can't use Test or Test::More because those modules
> rely on the features being tested. Most everything else can use
> Test::More. Barring any Unicode-related fiascos (of which I am proudly
> and blissfully unaware), they probably haven't bee
On Thu, 2003-10-16 at 10:46, Ovid wrote:
> I was browsing through the Perl core tests and I saw that some tests in the t/uni/
> directory used
> Test::More, but most other tests would explicitly 'print "ok 1\n"'.
>
> Is this to reduce the dependancy of the core tests on external modules (and if
I was browsing through the Perl core tests and I saw that some tests in the t/uni/
directory used
Test::More, but most other tests would explicitly 'print "ok 1\n"'.
Is this to reduce the dependancy of the core tests on external modules (and if so, why
does t/uni/
not follow the convention) or h
On 16 October 2003 05:47 Robert Spier wrote:
>> Yes. We've been thinking about this. It either needs stealing buildd
>> from Debian, having a box we don't mind destroying every so often, or
>> having a VMware virtual machine we can undo easily. What we need is
>> more free time ;-)
>>
>
> User
