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,b7cba06f5bdbaff2
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: Help performing timings
Date: 1995/04/07
Message-ID: <dewar.797263192@gnat>#1/1
X-Deja-AN: 100070417
references: <797193381snz@lynx1.demon.co.uk>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1995-04-07T00:00:00+00:00
List-Id: <comp.lang.ada>

the best way to deal with this timing issue is to interface to appropriate
C routines in your library. There are no portable routines with this kind
of accuracy -- the closest you can come is to use the real time package
in the annex, but I think the easiest thing is just to interface directly
to the C routine, which is particularly easy in GNAT, since the standard
GNAT types correspond to the C types (e.g. int = Integer). Or, if you want
to be more "correct", use Interfaces.C types.