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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,31d67020d4b04d5b X-Google-Attributes: gid103376,public From: "David C. Hoos, Sr." Subject: Re: Simple Real_Time.Time_Span question Date: 1998/10/13 Message-ID: <7003e4$534@hacgate2.hac.com>#1/1 X-Deja-AN: 400685278 References: <6vvsgo$rvo$1@nnrp1.dejanews.com> X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Organization: Hughes Aircraft Company Newsgroups: comp.lang.ada Date: 1998-10-13T00:00:00+00:00 List-Id: dennison@telepath.com wrote in message <6vvsgo$rvo$1@nnrp1.dejanews.com>... >I need to convert values of Ada.Real_Time.Time_Span into floating point >values for use in time-based simulation calculations. I'd think there *has* >to be a way to do this, but I don't see one. All I see is the ability to do >it indirectly via a conversion to Duration. But that looses the extra >accuracy of Time_Span, which was the whole point of using it in the first >place. > >Am I missing something? Yes, a couple of things, anyway, viz.: 1. I think you're talking about precision and not accuracy. 2. Since the types involved are defined in the RM as implementation-dependent, it is implementation-dependent whether there is any loss of precision going from Ada.Real_Time.Time_Span to Duration. In the case of the GNAT compiler, these both have resolution (precision) of one nanosecond. In fact, the specification for Ada.Real_Time.Time_Span in GNAT is new Duration. What other compilers may do is ....??