On Tue, 21 Jan 2003, Jonathan Stone wrote:

[JS: >You didn't read (or at least you did not quote) the second part of my
[JS: >suggestion which was that "micro" perhaps ought to be viewed as meaning
[JS: >"small", i.e., "subsecond" in the context of time.  So it's nanoseconds,
[JS: >now.
[JS:
[JS: Balderdash.  Our microtime is, in fact,
[JS:
[JS: 	microtime(struct timeval *tv)

*sigh*

[JS: not some blithering hypothetical abstract `high-resolution'' interface.
[JS: I'm suggesting that, if we are cleaning up high-resolution timekeeping,
[JS: that we start implementing
[JS:
[JS: 	void nanotime(struct timespec *)

That change from timeval to timespec was not made clear in your
original reply.  Sorry.

[JS: [or perhaps even a struct-returning function, since ANSI C has
[JS: supported those for years].

That's (can_of_worms (*(**)())[UINT64_MAX]) another;

				--*greywolf;
--
                 A _Real_ Operating System for _Real_ Hackers.

                   ______ _   __     __  ____ _____ ____
                  ______ / |_/ /__  / /_/ __ ) ___// __ \
                 ______ /  |/ / _ \/ __/ __  \__ \/ / / /
                ______ / /|  /  __/ /_/ /_/ /__/ / /_/ /
               ______ /_/ |_/\___/\__/_____/____/_____/

	 With many thanks to the NetBSD development team and UCB CSRG.