TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Proportional Font
Show HTML Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Date: Mon, 30 Oct 2000 15:02:09 -0600
Reply-To: Randy Brukardt <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
In-Reply-To: <01C0427F.38267C60@IGNITOR>
Content-Type: text/plain; charset="iso-8859-1"
From: Randy Brukardt <[log in to unmask]>
Parts/Attachments: text/plain (32 lines)
Pascal Obry writes:

> Stephen Leake writes:
>  >
>  > > What I would like to know is if anyone has programming (recently)
>  > > for real time and what the current performances and specifications
>  > > are for the Real_Time package?
>  >
>  > For any language:
>  >
>  > On Unix, 1 second.
>  >
>  > On Windows NT, 10 milliseconds.
>  >
>  > On VxWorks PowerPC, 100 microseconds (I think).
> I'am not sure what these values mean here. If it is the Clock
> precision then under NT it depends. The GNAT implementation use a
> performance counter and has a precision less than 1E-6 seconds, so
> far better than 10 milliseconds :)

For what it's worth, so does Janus/Ada. But ObjectAda and Rational Apex Ada
uses the standard clock tick for Calendar.Clock. Which is 10 milliseconds on
Windows NT; but if you run the same program (even the same executable) on
Windows 95/98, it is about 55 milliseconds.

All of which makes the original point: this depends completely on the target
system *and* implementation. The (original) question cannot be meaningfully
answered without knowing both the target system and implementation.