From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f3f07e9e53bcc4f6 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-12-20 07:10:49 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!fu-berlin.de!uni-berlin.de!tar-alcarin.cbb-automation.DE!not-for-mail From: dmitry@elros.cbb-automation.de (Dmitry A. Kazakov) Newsgroups: comp.lang.ada Subject: Re: FILETIME <-> Ada.Real_Time.Time conversions Date: Thu, 20 Dec 2001 15:10:46 GMT Message-ID: <3c21f386.108560406@News.CIS.DFN.DE> References: <3c1f3917.16015859@News.CIS.DFN.DE> <3C2057AF.323DFF5C@icn.siemens.de> <3c208dc5.16968437@News.CIS.DFN.DE> NNTP-Posting-Host: tar-alcarin.cbb-automation.de (212.79.194.111) X-Trace: fu-berlin.de 1008861047 18814798 212.79.194.111 (16 [77047]) X-Newsreader: Forte Free Agent 1.21/32.243 Xref: archiver1.google.com comp.lang.ada:18150 Date: 2001-12-20T15:10:46+00:00 List-Id: On Wed, 19 Dec 2001 15:06:18 GMT, "Steve Doiel" wrote: >I chose the same format for sending our time stamps across a network to >various machines. Currently these values are only decoded on Win32 PC's. > >It may be useful for you to know that VAX ELN (maybe VMS as well?) uses a >similar time stamp. The only difference is the time and date corresponding >to zero. > >Also note: it may not be possible (read probably isn't) to represent all >values of FILETIME as a Ada.Real_Time.Time value since the size of the >values may differ. As I recall the resolution of time in Ada.Real_Time is >not specified, but a minimum resolution and range is. We can definitely live with smaller range and/or precision. The real problem is that there is no correlation between epoch of Ada.Real_Time.Split and UTC. Regards, Dmitry Kazakov