The following is a summary of known issues of blead on VMS.
t/io/crlf_through.........................FAILED--unexpected output at
test 0
Can't find string terminator ")" anywhere before EOF at -e line 1.
T/IO/CRLF_THROUGH....FAILED--unexpected output at test 0
t/io/through..............................FAILED--unexpected output at
test 0
Can't find string terminator ")" anywhere before EOF at -e line 1.
Apparently new tests for VMS, failure not yet investigated, except that
when run with the test harness, a large number of the test fail.
t/op/goto.................................FAILED at test 53
Failure appears to be a known issue with VMS and other such tests are
marked either skip or todo for VMS. I have on my todo list to see if I
can get the test to pass as-is on VMS.
t/op/gv...................................FAILED at test 67
Failure appears to be a known issue with VMS and other such tests are
marked either skip or todo for VMS. I have on my todo list to see if I
can get the test to pass as-is on VMS.
lib/Archive/Tar/t/04_resolved_issues......FAILED at test 9
Failure is because it has a directory with dots in the name and the
traditional VMS filename parsing can not handle that. The PERL.EXE for
OpenVMS can handle such directory specifications, and will handle them
better when a feature is set. Pathtools currently can not handle those
file specifications.
Fixing Pathtools requires that Pathtools know what Compatibility mode
that the VMS C library is in.
lib/ExtUtils/t/basic......................FAILED at test 67
This failure is because of a known "Feature" in the GNV product which is
violating HP conventions for logical name use. A bug report has been
filed with the GNV product. In the mean time, the
DECC$UNIX_PATH_BEFORE_LOGNAME logical name needs to be set for this test
to pass. When this logical name is set, the Perl debugger does not
function.
A fix is needed for the Perl debugger once the failure cause is found,
and a fix is needed for GNV. A quick test is showing that GNV should
not be using the logical name BIN that is causing the conflict.
lib/ExtUtils/t/Command....................FAILED--unexpected output at
test 3
Known issue in the underlying test programs not handling undefined
values in comparisons correctly.
lib/ExtUtils/t/Manifest...................FAILED--unexpected output at
test 12
Known issue in the underlying test programs not handling undefined
values in comparisons correctly.
lib/File/Copy.............................FAILED at test 20
Known issue of the VMS filesystem. This test can be made to pass on VMS
when used with the ODS-5 file system and that volume has UNIX timestamps
enabled, and the C library has been told of this. More details have
previously been published. I have not changed the test as I am looking
for a way for the test to determine when it is valid on VMS and when it
is not.
lib/Math/BigInt/t/mbi_rand................FAILED--unexpected output at
test 48
Known issue with VMS pipe handling. I have not changed the test because
it is on my todo list to see if I can make the VMS issue go away.
lib/Pod/t/Usage...........................FAILED at test 6
# cmd = eagle$dqa0:[project_root.][perl-blead.t]perl.;1 "-I../lib"
"-MPod::Usage" -e "pod2usage({ -verbose => 0, -exit => 2,
-output => q{_NLA0:}, -input => q{[-.lib.pod.t]usage.t} })"
not ok 6 - Exit status of pod2usage()
LIB/POD/T/USAGE....FAILED at test 6
Looks like my clean up of error/exit handling still needs more work.
lib/Test/Simple/t/is_deeply_fail..........FAILED at test 73
not ok 73 - right diagnostic
Need to investigate:
t/pod/pod2usage2..........................FAILED at test 2
not ok 2 - Exit status pod2usage ()
T/POD/POD2USAGE2....FAILED at test 2
This test appears new to VMS. Need to investigate.
Also noticed:
* The perl5db_pids feature does not work on VMS unless Perl is being run
under the bash shell.
* MakeMaker is generating a false command which breaks rebuilding perl
on VMS unless an alias is created that causes false to return a
success.
The intent of the false command is to indicate a build failure to the
caller of the makefile. But because of the way that the VMS shell
handles such errors, it totally aborts the build.
If MakeMaker sets up the false command to work on VMS as it does on
other perls, then the DCL build procedures for Perl need to be fixed
to expect that behavior.
* REALCLEAN target has many syntax errors while it is running and still
leaves some *_OLD files behind. IMHO, the syntax errors indicate that
the rules for the target are not being created correctly.
* Documentation update may be needed about timezone issues, which may
not be VMS specific. If you are changing to/from DST with a
non-standard timezone, you should use the ZIC utility or equivalent
for your platform to create a new timezone to match what you are doing
or some programs that work with time values may produce incorrect
results, and this includes Perl programs.
-John
[EMAIL PROTECTED]
Personal Opinion Only
