Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site pegasus.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!pegasus!hansen
From: hansen@pegasus.UUCP (Tony L. Hansen)
Newsgroups: net.sources.bugs
Subject: Re: How do I compile ttype?
Message-ID: <2671@pegasus.UUCP>
Date: Mon, 9-Dec-85 10:15:42 EST
Article-I.D.: pegasus.2671
Posted: Mon Dec  9 10:15:42 1985
Date-Received: Tue, 10-Dec-85 06:22:27 EST
References: <965@turtlevax.UUCP> <13500001@hpspkla.UUCP> <1752@teddy.UUCP>
Reply-To: hansen@pegasus.UUCP (60545451-Tony L. Hansen;LZ 3B-315;6243)
Organization: AT&T-IS Labs, Lincroft, NJ
Lines: 20
Keywords: time(2), ftime(2), times(2)
Summary: use times(2) to get < 1 sec on Sys III/V

< If your system does not have timeb.h, then it also doesn't have ftime(),
< the function that uses the type "struct timeb".  If you don't have this
< function, then you need a total rewrite of the program (if that is even
< possible)!  ftime returns time in units SMALLER than one second.  System
< III/V do not support this functionality (a major flaw, in my opinion) making
< timing tasks such as in ttype much more difficult.

To get < 1 second timing information on System III/V, one can make use of
the times(2) system call. In addition to filling in a structure with
information that is not needed for this purpose, it returns the elapsed real
time, in 60ths or 100ths of a second depending on the processor, since an
arbitrary (fixed per process) point in the past.

By using this system call, I have been able to get the functionality needed
for programs such as ttype.

I'm not going to debate flawness issue.

					Tony Hansen
					pegasus!hansen