Re: Ada.Real_Time Vs. Ada.Calendar

"Jeffrey R. Carter" <spam.not.jrcarter@xxxxxxxxxxxxxxxx> writes:

In general, you can't count on them having any meaningful
relationship. Real_Time may be a count of ticks since the program
started, for example, while Calendar must be a date and time CE.

And I don't think it would be right to expect the relationship to be
constant, either -- Ada.Calendar might be synchronised with an
external time shource and might not be monotonic, whereas Real_Time
ought to be monotonic.
.

Relevant Pages

  • Re: Extended-Range Time Type
    ... it is a count of 2^-29 second ticks instead of 2-nanosecond ticks, ... and it includes leap seconds in its representation. ... Gregorian calendar. ... There's problems with leap seconds too. ...
    (comp.std.c)
  • Re: The entrance that solves
    ... whole) ought to have brought the house down immediately, ... which do not deal with any abbreviations. ... calendar is mainly a logical improvement. ...
    (sci.lang)
  • Re: When did MTR become so politicized?
    ... Yes there is egg on my face. ... Guess I really ought to check the calendar ... ... for some reason I was all screwed up with my days & dates last week. ...
    (misc.transport.road)
  • Re: Cannot sync calendar anymore
    ... the rest syncs very well and Calendar finds lots of entries to be ... synchronised and seems to start sync but after a few seconds ticks as if it ... "To proceed ActiveSync must remove all calendar entries from your PPC, ... Sync always worked well until recently. ...
    (microsoft.public.pocketpc.activesync)
  • Re: Cannot sync calendar anymore
    ... the rest syncs very well and Calendar finds lots of entries to be ... synchronised and seems to start sync but after a few seconds ticks as if it ... "To proceed ActiveSync must remove all calendar entries from your PPC, ... Sync always worked well until recently. ...
    (microsoft.public.pocketpc.activesync)