[q-lang-cvs] q/modules/clib system.q,1.7,1.8

[Albert G. <ag...@us...>]

Update of /cvsroot/q-lang/q/modules/clib
In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv3296

Modified Files:
	system.q 
Log Message:
comment change

Index: system.q
===================================================================
RCS file: /cvsroot/q-lang/q/modules/clib/system.q,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** system.q	23 Feb 2008 08:42:26 -0000	1.7
--- system.q	23 Feb 2008 10:12:59 -0000	1.8
***************
*** 754,764 ****
     resolution of the given timer. The nanosleep function sleeps for the
     specified amount of nanoseconds, while the nanosleep_until function sleeps
!    until the given (absolute) time arrives. (Just like the sleep function,
!    these functions may exit early if a signal is delivered to the process; see
!    the manual for details.) In case of any error condition, these functions
!    will set errno accordingly.
  
     For each of the functions you have to specify an integer-valued timer
!    id. In the current implementation, the following timers are supported:
  
     - CLOCK_REALTIME: The system clock, measured in nanosecs since the epoch.
--- 754,763 ----
     resolution of the given timer. The nanosleep function sleeps for the
     specified amount of nanoseconds, while the nanosleep_until function sleeps
!    until the given (absolute) time arrives. In case of an error condition,
!    these functions will set errno accordingly.
  
     For each of the functions you have to specify an integer-valued timer
!    id. In the current implementation, the following timers are supported (the
!    corresponding constants are defined at the beginning of this module):
  
     - CLOCK_REALTIME: The system clock, measured in nanosecs since the epoch.
***************
*** 774,781 ****
       might be unreliable on SMP systems, see clock_gettime(3) for details.)
  
!    Only CLOCK_REALTIME is guaranteed to be available (on systems which
!    implement the highres timers at all, that is). If a given clock is
!    unavailable on the host system, the corresponding id will be () (if
!    CLOCK_REALTIME is (), then the highres timers are not supported at all).
  
     Moreover, if CPU timers are available, then the process_cpu_clockid and
--- 773,780 ----
       might be unreliable on SMP systems, see clock_gettime(3) for details.)
  
!    Only CLOCK_REALTIME is guaranteed to exist (on systems which implement the
!    highres timers at all, that is). If a given clock is unavailable on the
!    host system, the corresponding id will be () (if CLOCK_REALTIME is (), then
!    the highres timers are not supported at all).
  
     Moreover, if CPU timers are available, then the process_cpu_clockid and
***************
*** 787,794 ****
     actual resolutions depend on your system setup and will typically be much
     coarser (for the system and monotonic clocks, they are usually in the
!    milliseconds range on current PCs). Also, you must consider system
!    latencies which might cause calls to nanosleep and nanosleep_until to wake
!    up late on occasions (use realtime scheduling priorities to mitigate these
!    effects). */
  
  public extern nanotime ID, nanores ID;
--- 786,792 ----
     actual resolutions depend on your system setup and will typically be much
     coarser (for the system and monotonic clocks, they are usually in the
!    milliseconds range on current PCs). Also, be aware that system latencies
!    might cause calls to nanosleep and nanosleep_until to wake up late (use
!    realtime scheduling priorities to mitigate these effects). */
  
  public extern nanotime ID, nanores ID;