Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: "John M. Aldrich" <fighteer AT cs DOT com>,
        DJGPP Workers Mailing List <djgpp-workers AT delorie DOT com>
From: Nate Eldredge <nate AT cartsys DOT com>
Subject: Re: rawclock()
Date: Sun, 10 May 1998 20:55:04 -0700
Message-ID: <19980511035425.AAN4598@ppp107.cartsys.com>
Precedence: bulk

At 08:55  5/10/1998 -0400, John M. Aldrich wrote:
>I was unable to find any reference to this in the djgpp-workers archives
>or the bug tracker.  If this has been discussed before, I apologize.
>
>There's a bug in either the libc docs for rawclock() or the function
>itself.  According to the docs:
>
>---snip---
>     unsigned long rawclock(void);
>
>Description
>-----------
>
>Returns the number of clock tics (18.2 per second) since midnight.
>---snip---
>
>However, according to the source, rawclock() actually returns the number
>of tics since the first call to itself in the program.  This seems to
>exactly duplicate the functionality of clock(), so I assume that the
>function itself is in error.  A patch is attached.

I reported and patched this quite a while ago (exactly the same way as you,
incidentally). It has found its way into the 2.02 alpha (which, btw, I find
it's helpful to check before reporting a bug).

I think it was before I knew the existence of djgpp-workers, so it took
place on the main djgpp list. Hence the lack of info in the archives.


Nate Eldredge
nate AT cartsys DOT com