Re: Darwin - looking good

2001-09-20 Thread Michael G Schwern

On Thu, Sep 20, 2001 at 12:42:13AM +0100, Robin Houston wrote:
 I only had one real problem with Parrot on Darwin, which really has
 nothing to do with Darwin at all.  The first time I tried to make test
 I got a slew of errors about Test::More, so I diligently went to CPAN
 and downloaded the latest version.

The latest version of the Test-More tarball should have blown up in
your face with a big Don't use this, download Test-Simple instead! 
to prevent exactly this sort of thing from happening.  For some reason
that last version doesn't seem to have made it into
modules/by-module/Test/, it's just sitting in my author directory.

Sorry for the inconvenience, I'll go poke the CPAN folks.


 Are there any plans to remove the dependency of Parrot::Test on
 non-core modules? It's bound to be a stumbling block for quite
 a few people, surely? If not, I'll contribute a patch which
 makes the failure more graceful and informative.

These actually are core, but not until 5.7.2.  And we don't want to
take a Great Leap Backward to Test.pm.

For *exactly* such a contingency (I sound like an Acme saleman now) we
have Test-SDK (remember the SDKs?) which includes new-enough versions
of Test::More, Test::Simple, Test::Inline and Test::Harness in one
handy, easy to install tarball for those of you that don't use the
CPAN shell.

As a third alternative, you can simply distribute Test::Simple/More
(and even the new versions of Test::Harness) as part of parrot, same
as you do Parrot::Test.  That involves the least work for the test
runner.


I'd suggest creating a lib/ directory and moving Parrot/ into it now
before you get a proliferation of individual Perl module directories.
And change the Makefile to this:

PERL = perl
PERLRUN = $(PERL) -Ilib

test:
$(PERLRUN) t/harness

and the other targets that use $(PERL) change to $(PERLRUN).


I could do this myself.  What's the best way to submit a bunch of
file/directory moves?


-- 

Michael G. Schwern   [EMAIL PROTECTED]http://www.pobox.com/~schwern/
Perl6 Quality Assurance [EMAIL PROTECTED]   Kwalitee Is Job One
purl Hey, Schwern!  THERE IS A HUGE GAZORGANSPLATTEDFARTMONGERING-
LIGHTENINGBEASTASAURSOPOD BEHIND YOU!  RUN, BEFORE IT GAFLUMMOXES YOUR
INNARDLYBITS!



Re: Darwin - looking good

2001-09-20 Thread Simon Cozens

On Thu, Sep 20, 2001 at 04:00:02AM -0400, Michael G Schwern wrote:
 The latest version of the Test-More tarball should have blown up in
 your face with a big Don't use this, download Test-Simple instead! 

This is irrelevant in this case, because that's still a non-core module.

 These actually are core, but not until 5.7.2.

Which means not until 5.6.2, which means we're stuffed *now*. That
doesn't help much either.

 As a third alternative, you can simply distribute Test::Simple/More
 (and even the new versions of Test::Harness) as part of parrot

You're just trying to take over the world now.

-- 
And tomorrow will be like today, only more so.
-- Isaiah 56:12, New Standard Version



Darwin - looking good

2001-09-19 Thread Robin Houston

I only had one real problem with Parrot on Darwin, which really has
nothing to do with Darwin at all.  The first time I tried to make test
I got a slew of errors about Test::More, so I diligently went to CPAN
and downloaded the latest version. It claimed dependency on Test::Simple,
which claimed dependency on an updated version of Test::Harness. So I
downloaded, built and installed all those. Then I tried the Parrot tests
again. Still no joy. I eventually discovered that newer versions of
Test::Simple *include* Test::More, and that my installing Test::More
had overwritten the _later_ version that was installed when I installed
Test::Simple. So I reinstalled Test::Simple, and:

[robin@robin parrot]$ make test
perl t/harness
t/op/basic..ok, 1/2 skipped:  label constants unimplemented in assembler 
t/op/integerok   
t/op/number.ok, 2/23 skipped: various reasons
t/op/string.ok, 1/5 skipped:  I'm unable to write it!
t/op/trans..ok   
All tests successful, 4 subtests skipped.
Files=5, Tests=74, 31 wallclock secs (14.69 cusr + 10.05 csys = 24.74 CPU)

which looks okay to me.

Are there any plans to remove the dependency of Parrot::Test on
non-core modules? It's bound to be a stumbling block for quite
a few people, surely? If not, I'll contribute a patch which
makes the failure more graceful and informative.

 .robin.