Timer

Returns the amount of time that has passed since a static reference point.

Syntax
	KeyPgDeclareDeclare KeyPgFunctionFunction Timer ( ) KeyPgAsAs KeyPgDoubleDouble

Usage
	result = Timer

Return Value
	Returns a KeyPgDoubleDouble precision result with the time, in seconds, since a 
	static reference point.

Description
	The Timer function is useful for finding out how long a section of code 
	takes to run, or for control the timing of your code.  To find out how 
	much time has passed between two points in your program, you can record 
	the value of Timer at the start and end points, and then subtract the 
	start value from the end value.

	On some platforms, the value of Timer resets to zero at midnight (see 
	below), so if the start and end time are on either side of the reset 
	point, the difference will be negative.  This could cause unexpected 
	behavior in some programs.  In those cases, adding 86400 (the number of 
	seconds in 24 hours) to the difference should return the correct result. 
	If the time taken is longer than a day, then it will be also be 
	necessary to check the number of days that have elapsed.

	The value returned by Timer is NOT affected by the automatic changing of 
	the system clock, in Spring and Autumn, for DST (Daylight Savings Time).

Example
	'' Example of using TIMER function 
	'' Note: see text about correct waiting strategies
	Dim Start As Double
	Print "Wait 2.5 seconds."
	Start = Timer
	Do
	   Sleep 1, 1
	Loop Until (Timer - Start) > 2.5
	Print "Done."

Platform Differences
	* On Win32 and Linux, if the program must wait for periods of 0.1 
	  seconds or more, KeyPgSleepSleep should be used, this allows other programs to 
	  run during the waiting period. For shorter delays, a loop using TIMER 
	  can be more precise.
	* The reference point chosen varies, depending on the platform.  On 
	  Windows, the time is measured relative to the point the computer was 
	  booted up.  On DOS, the time is measured relative to Jan 1 1970.

	Note for DOS users: today, the number of seconds since 1970 is in excess 
	of 10^9, and is therefore unsuitable for storing in KeyPgSingleSingle-precision 
	variables, also it shouldn't be multiplied (to get 1/10 seconds or so) 
	and stored in 32-bit integer variables then

	* The precision of TIMER varies, depending on the computer used.  If 
	  the processor has a precision timer (as the Performance Counter 
	  Pentium processors from Intel have) and the OS uses it, the precision 
	  is linked to the processor clock and microseconds can be expected. 
	  With older processors (386, 486), and always in DOS, the resolution is 
	  1/18 second.

	* Usage of TIMER can cause disk accesses in DOS, see http://www.freebasic.net/forum/viewtopic.php?t=12985forum for analysis 
	  and solutions

Differences from QB
	* In QB, TIMER returned the number of seconds from last midnight, and 
	  its accuracy was 1/18 secs

See also
	* KeyPgTimeTime
	* KeyPgSleepSleep

