At 5:34 PM -0400 4/2/06, John E. Malmberg wrote: >Craig A. Berry wrote: >>At 12:43 PM -0400 4/2/06, John E. Malmberg wrote:
>>>The ACP interface that is used for the work around to not having a >>>built in utime() can not handle EFS file specifications. It needs to >>>have the on-disk file specification. >> >>But won't do_rmsexpand() take care of that? > >Yes, but then you do not pick up setting the DECC$EFS_FILE_TIMESTAMPS values. >Using the CRTL utime() picks up both. I've committed #27706, which uses the CRTL utime() for 7.3 and later, but the existing ACP interface code for anything previous. The presence of utime.h does not help, as it became available before the utime() function did. It looks to me like the CRTL utime() does the same thing the old code does on ODS-2 or ODS-5 without access dates. On ODS-5 with access dates enabled, we'll get the same behavior any other C program calling utime() will get. I think we may want to enable DECC$EFS_FILE_TIMESTAMPS by default in Perl, though that remains to be tested and checked for consistency with our stat() implementation. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
