diff options
| author | Craig A. Berry <craigberry@mac.com> | 2009-02-21 14:46:27 -0600 |
|---|---|---|
| committer | Craig A. Berry <craigberry@mac.com> | 2009-02-21 14:46:27 -0600 |
| commit | ec4d613228615e5a9cc9bc190eb78ec02aadcda0 (patch) | |
| tree | bfe5723e36732a8799f45613fbedf1cc26f41c20 /time64_config.h | |
| parent | 3aaf6557bbee1b4253a365839e7074c1efc18213 (diff) | |
| download | perl-ec4d613228615e5a9cc9bc190eb78ec02aadcda0.tar.gz | |
Use "system" gmtime in time64 on VMS so C<vmsish 'time'> pragma works.
It's not really the system gmtime; it's the homegrown one in vms/vms.c
that checks hints and does shifting between UTC and local time when
requested.
Diffstat (limited to 'time64_config.h')
| -rw-r--r-- | time64_config.h | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/time64_config.h b/time64_config.h index 4032acd215..6a1cd9d063 100644 --- a/time64_config.h +++ b/time64_config.h @@ -60,10 +60,13 @@ USE_SYSTEM_GMTIME Should we use the system functions if the time is inside their range? Your system localtime() is probably more accurate, but our gmtime() is - fast and safe. + fast and safe. Except on VMS, where we need the homegrown gmtime() + override to shift between UTC and local for the vmsish 'time' pragma. */ #define USE_SYSTEM_LOCALTIME -/* #define USE_SYSTEM_GMTIME */ +#ifdef VMS +# define USE_SYSTEM_GMTIME +#endif /* SYSTEM_LOCALTIME_MAX |