Re: MM_VMS and File::Spec::VMS.pm intertanglement.
[email protected] ("John E. Malmberg")
| Newsgroups | perl.perl5.porters,perl.vmsperl |
|---|---|
| Message-ID | <[email protected]> |
Michael G Schwern wrote: > John E. Malmberg wrote: >> The comments for eliminate_macros() and fixpath() in File::Spec::VMS >> imply that they are only used in older versions of Make Maker that does >> not contain them. >> >> Putting a print STDERR statement shows that is not the case, that the >> methods of those names contained in File::Spec::VMS are used unless they >> are called by MM_VMS. >> >> I am now trying to update File::Spec to handle VMS EFS character >> specifications and GNV (GNU is not VMS) Unix compatibilty mode, so I >> will need to first update File::Spec::VMS, and then MM_VMS later. >> >> In the EFS (Extended character set) mode, in addition to handling the >> extended character set, the routines will return Unix syntax for Unix >> input and VMS syntax for VMS input. >> >> For cases where there is no input, or the input does not indicate the >> output format, then the output will be in VMS syntax unless the UNIX >> compatibilty mode is also on. If that mode is on, then ambigous output >> will be in Unix syntax. >> >> This appears to match the expectation of most of the Perl scripts that I >> have worked on getting ported to VMS. > > Do you need anything, or was that just an FYI/RFC? Mostly a FYI/RFC. Would there be an issue if File::Spec::VMS get the changes before MM_VMS? The last time I did this with Perl 5.8.6/7, I just made the changes to get the tests to pass. This time I am trying to get the operations to be as correct as possible. So I need to re-write File::Spec::VMS so that in EFS mode it almost never calls vmsify or unixify, and I do not know how long that will take. -John [email protected] Personal Opinion Only