I'm examining the feasibility of making VMS::Filespec available to all
installations (makes testing File::Spec::VMS a whole lot easier) and
ran vms/ext/filespec.t on my OS X box. I got some failures but none
of them seem to be related to my running on Unix. They all appear to be
genuine bugs in t
Michael G Schwern <[EMAIL PROTECTED]> wrote on 07/08/2005 08:09:40 PM:
> I'm examining the feasibility of making VMS::Filespec available to all
> installations (makes testing File::Spec::VMS a whole lot easier) and
> ran vms/ext/filespec.t on my OS X box. I got some failures but none
> of them se
On Fri, Jul 08, 2005 at 08:31:59PM -0400, [EMAIL PROTECTED] wrote:
> I just ran it on IA64 with a perl 5.8.7 kit and it went ok:
Hmm. Here's the easiest of my failures to analyze:
not ok 52 - vmsify('.../'): '[]'
# Failed at ../vms/ext/filespec.t line 24
# got '[]'
# expected '[...]
At 6:09 PM -0700 7/8/05, Michael G Schwern wrote:
>
>Ah ha! So basically the Perl code isn't normally being used and thus has
>fallen way out of sync with the vms.c code?
From
$ perldoc VMS::Filespec:
If you're running under VMS, the routines in this package are special,
in that they'r
Michael G Schwern wrote:
I'm examining the feasibility of making VMS::Filespec available to all
installations (makes testing File::Spec::VMS a whole lot easier) and
ran vms/ext/filespec.t on my OS X box. I got some failures but none
of them seem to be related to my running on Unix. They all app
Michael G Schwern wrote:
On Fri, Jul 08, 2005 at 08:31:59PM -0400, [EMAIL PROTECTED] wrote:
I just ran it on IA64 with a perl 5.8.7 kit and it went ok:
Hmm. Here's the easiest of my failures to analyze:
not ok 52 - vmsify('.../'): '[]'
# Failed at ../vms/ext/filespec.t line 24
# g
