Re: FILETIME <-> Ada.Real_Time.Time conversions

["Steve Doiel" <nospam_steved94@attbi.com>]

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" <dmitry@elros.cbb-automation.de> 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