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-19 07:06:19 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.mathworks.com!wn3feed!worldnet.att.net!204.127.198.204!attbi_feed4!attbi_feed3!attbi.com!rwcrnsc53.POSTED!not-for-mail From: "Steve Doiel" Newsgroups: comp.lang.ada References: <3c1f3917.16015859@News.CIS.DFN.DE> <3C2057AF.323DFF5C@icn.siemens.de> <3c208dc5.16968437@News.CIS.DFN.DE> Subject: Re: FILETIME <-> Ada.Real_Time.Time conversions X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: Date: Wed, 19 Dec 2001 15:06:18 GMT NNTP-Posting-Host: 204.127.202.216 X-Complaints-To: abuse@attbi.com X-Trace: rwcrnsc53 1008774378 204.127.202.216 (Wed, 19 Dec 2001 15:06:18 GMT) NNTP-Posting-Date: Wed, 19 Dec 2001 15:06:18 GMT Organization: AT&T Broadband Xref: archiver1.google.com comp.lang.ada:18094 Date: 2001-12-19T15:06:18+00:00 List-Id: 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. SteveD "Dmitry A. Kazakov" wrote in message news:3c208dc5.16968437@News.CIS.DFN.DE... [snip] > > Presently parts of the system are under implementation in Ada 95 *not* > under Win32. There is no designated platform. It should be portable. > So the question reappears. It is relatively easy to convert FILETIME > to Ada.Calendar.Time provided that Ada.Calendar.Split and Time_Of are > dealing with UTC [??]. Yet there is a hint in Ada Rationale that > Ada.Calendar.Time might suffer jumps because of daylight savings > [shudder]. At the same time, it seems that Ada.Real_Time.Time was very > carefully designed to prevent any attempt to correlate it with any > external clock [??]. So the problem. > > Regards, > Dmitry Kazakov