In script t/op/goto.t, tests 53 and 54 are failing because of an
unexpected new line that VMS has apparently been requested to add.
In script t/op/gv.t, test 67 is spawning a multi-line perl program as an
argument to a spawned perl command. The spawned command is returning a
success with no output:
not ok 67 - DESTROY was called
# Failed at ./test.pl line 249
# got ''
# expected /(?-xism:^Farewell M=SCALAR)/
In t/op/magic.t, test 7 is failing because the first time that
keys(%ENV) is called, the first environment variable in the hash is
reported twice. This does not occur on subsequent calls to keys(%ENV).
The script is unexpectedly exiting after test 55 with the following text:
ok 55
Can't make list assignment to %ENV on this system at [-.T.OP]magic.t
line 441, <DATA> line 17.
at [-.T.OP]magic.t line 441
Can't make list assignment to %ENV on this system at [-.T.OP]magic.t
line 441, <DATA> line 17.
I also note that when the script exits with an error, and I use q to
quit the debugger, the PERLDB_PIDS environment variable is not cleared.
This use of process IDs does not work as intended on VMS in any case.
-John
[EMAIL PROTECTED]
Personal Opinion Only
