* B19: clock() problem
@ 1998-10-19 15:56 Stephane Pelchat
0 siblings, 0 replies; 2+ messages in thread
From: Stephane Pelchat @ 1998-10-19 15:56 UTC (permalink / raw)
To: gnu-win32
Hi all,
I'm currently developping a game server application with GNU-Win32. I'm
using the clock() function to synchronize the events in the server but the
function doesn't seem to be implemented, and always returns a similar
value from one run to the other. Other time functions like time() are
working just fine.
I've downloaded the latest versions I could found (Beta 19.1 for
'cygwinb19.dll' and Beta 19 for the other libraries like 'libc.a'). I'm
also including <time.h> from the default include directory.
Any help would be appreciated, and keep up the good work, thx!
Stephane Pelchat
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: B19: clock() problem
@ 1998-10-20 17:33 N8TM
0 siblings, 0 replies; 2+ messages in thread
From: N8TM @ 1998-10-20 17:33 UTC (permalink / raw)
To: spelchat, gnu-win32
In a message dated 10/20/98 7:37:34 AM Pacific Daylight Time,
spelchat@videotron.ca writes:
> clock() function to synchronize the events in the server but the
> function doesn't seem to be implemented
It returns 0 on W95. For a stop gap, I've been using the cpu_time()/dtime()
function from libf2c in Mumit Khan's binary, which is written in terms of
WinAPI QueryPerformance calls. You might examine his libf2c patch file to see
how we did that.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1998-10-20 17:33 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-10-19 15:56 B19: clock() problem Stephane Pelchat
1998-10-20 17:33 N8TM
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).