On Tuesday, September 30, 2003, at 05:34PM, Barry Treahy, Jr. <[EMAIL PROTECTED]> wrote:
>If I understand (aka guess) properly, at run time the default calls to >VMS::Filespec are basically being redirected to hardcoded C by way of >the newXSproto calls, which might explain why my debug statements in >Filespec.pm are not working. First, is this what is happening? There are two ways to get at the VMS::Filespec methods. If you are on VMS, the redirection to the C code in vms.c is as you have surmised. This has some speed advantages and allows the use of native services. On other platforms, the pure Perl versions of the same methods kick in so that it is possible to manipulate VMS file specs without having a VMS system. Thanks for your efforts to get CPAN working. You'll want to have a look at Chuck Lane's VMS::FileUtils module that creates ODS-2 safe names, among other things: http://search.cpan.org/CPAN/authors/id/C/CL/CLANE/VMS-FileUtils_0.014.tar.gz IIRC, part of the problem with CPAN may be that external utilities also need additional tweaking. For example, you may need a version of gunzip that does command-line redirection without help from the pipe command.
