X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=time64_config.h;h=42cc12c88e427a48ebe18c9407be890fe3fbdd07;hb=9758931364444385e32f6e1abf2e6aba4ddbd236;hp=c22a1153e259df4218bbc7c69dfb847aa6a3a9c0;hpb=b86b480f7301a8816081189c89b366a79ab9909f;p=p5sagit%2Fp5-mst-13.2.git

diff --git a/time64_config.h b/time64_config.h
index c22a115..42cc12c 100644
--- a/time64_config.h
+++ b/time64_config.h
@@ -7,11 +7,18 @@
    Sensible defaults provided.
 */
 
+/* Debugging
+   TIME_64_DEBUG
+   Define if you want debugging messages
+*/
+/* #define TIME_64_DEBUG */
+
+
 /* INT_64_T
-   A 64 bit integer type to use to store time and others.
+   A numeric type to store time and others. 
    Must be defined.
 */
-#define INT_64_T                Quad_t
+#define INT_64_T                NV
 
 
 /* USE_TM64
@@ -53,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
@@ -67,9 +77,9 @@
    can handle.  We will use your system functions if the time falls
    inside these ranges.
 */
-#define SYSTEM_LOCALTIME_MAX    LOCALTIME_MAX
-#define SYSTEM_LOCALTIME_MIN    LOCALTIME_MIN
-#define SYSTEM_GMTIME_MAX       GMTIME_MAX
-#define SYSTEM_GMTIME_MIN       GMTIME_MIN
+#define SYSTEM_LOCALTIME_MAX    CAT2(LOCALTIME_MAX,.0)
+#define SYSTEM_LOCALTIME_MIN    CAT2(LOCALTIME_MIN,.0)
+#define SYSTEM_GMTIME_MAX       CAT2(GMTIME_MAX,.0)
+#define SYSTEM_GMTIME_MIN       CAT2(GMTIME_MIN,.0)
 
-#endif TIME64_CONFIG_H
+#endif /* TIME64_CONFIG_H */