The purpose of the static variable is to keep the time when high
performance counters were started. (This appears to be at boot time.)
This is a one time initialization job, no harm should appear even
in a multi thread environment.
When initialization is done (only once per process), then funct
Does this variable need to be a true global?
If it does then it has to be mutexed. Having said that if two threads want
to change it and you think it doesn't really matter which one will "win"
then you can probably live without the mutex.
Andi
At 10:35 AM 2/5/2001 +, James Moore wrote:
>
> I don't think you should be using static variables in the
> functions. Don't
> forget that you might have more than one thread accessing this
> function at
> a time (unless you came to the conclusion that a race here can't
> do any harm).
I dont think race conditions here will do any real harm
I don't think you should be using static variables in the functions. Don't
forget that you might have more than one thread accessing this function at
a time (unless you came to the conclusion that a race here can't do any harm).
Andi
At 03:52 PM 2/4/2001 +, James Moore wrote:
>jmoore
works now. Ill look and see if theres a way to make it as accurate
as the *nix version.
James
> -Original Message-
> From: James Moore [mailto:[EMAIL PROTECTED]]
> Sent: 04 February 2001 15:53
> To: [EMAIL PROTECTED]
> Subject: [PHP-CVS] cvs: php4 /win32 time
jmoore Sun Feb 4 07:52:33 2001 EDT
Modified files:
/php4/win32 time.c
Log:
Fix for time.c under win32. Patch By: "Vanhanen, Reijo" <[EMAIL PROTECTED]>
@- microtime under windows now returns accurate values (James)
Index: php4/win32/time.c
diff -u p
6 matches
Mail list logo
