At 8:10 AM +0200 11/21/03, Saku Setala wrote:
>Same environment as previous, perl 5.9.0 failed tests
>
>t/op/tie.............................FAILED at test 21
>ext/Filter/t/call....................FAILED at test 1
>ext/IO/t/io_udp......................FAILED at test 1
>ext/Socket/t/Socket..................FAILED at test 0
>lib/File/Copy........................FAILED at test 4
>lib/strict...........................FAILED at test 106
>lib/vmsish...........................FAILED at test 25
>Failed 7 test scripts out of 734, 99.05% okay.

I know quite a few people already know this,  but there are also some
new folks on the list, so I thought I should explain what 5.9.0 is
before commenting on its status.  5.9.0 (because its minor version is
an odd number) is a development release.  You should get very clear
warnings about the development status at configuration time.  Some
5.9.x changes will be integrated back into the 5.8.2 (or even 5.6.x)
production streams, but others will not see the light of day in a
production release until 5.10.0.  Perl development releases may
contain experimental features that never make it into production
releases, or may contain new features that are only half-debugged, or
may have reimplementations of old features that end up getting yanked
because the old implementation was better.  All of which is to say,
have fun, but don't use development releases in production, and don't
be surprised if things that used to work are under construction.

That said, 5.9.0 isn't looking as bad as I expected.  Several of
those failures are due to a change that broke the way we use
fgetname().  Some need further exploration, though.  If anyone is so
inclined, please use the current latest development patchlevel
(known as bleadperl) since there have been a lot of further changes
since 5.9.0.  You can get bleadperl via:

$ rsync -avz ftp.linux.activestate.com::perl-current bleadperl

You'll need to use a unix/linux/OS X machine that has rsync, zip up
the tree and move it to a VMS machine.  Be sure to check file
protections since the source repository is by default read only.
There is an rsync for VMS under development -- see vmsnet.vms-posix
-- but I don't think it's ready to use yet.

-- 
________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser

Reply via email to