Mark Berryman wrote:
I am curious. Why would you not want to simply define _USE_STD_STAT?
Perl currently is coded to expect only the behavior of the traditional
but non standard compliant stat structure and related calls and then
give an illusion that the stat structure is compliant.
Most of the infrastructure is in place for the enabling it, but I want
to get all the long filename support in first.
What is needed is that the stat/fstat calls will need to cache the short
path and filename being tested in space that is now reserved in the
mystat structure. The perl_cando code will then reference this instead
of a static cache that is used now for both stat and fstat().
At that point, I do not think that the static cache will be needed, and
also after that change, there should be no reason for VMS.C to track the
differences between the two stat structures.
Is it because this feature is not available on the VAX?
No, but it is not available before OpenVMS 8.2 and requires 64 bit
support by the compiler.
How old of a VMS version does this version of Perl need to compile on?
I am not sure. I think I have seen some VMS 7.2-x build results recently.
DEC/COMPAQ/HP C that is capable of building Perl is available back to
5.5-2, but it would take me a bit to set up a system that old.
Now as to why to add support for the standard compliant stat structure
is that the dev_t information can be interchanged between applications
to identify when multiple filenames resolve to the same file.
There may be other cases where having the correct dev_t value could be
significant.
-John
[EMAIL PROTECTED]
Personal Opinion Only
