Cygwin with clock_gettime and CLOCK_MONOTONIC - gives always 0

Steve Kargl sgk@troutmask.apl.washington.edu
Thu Apr 11 23:17:00 GMT 2013


On Thu, Apr 11, 2013 at 11:23:42PM +0100, N.M. Maclaren wrote:
> On Apr 11 2013, Steve Kargl wrote:
> >On Thu, Apr 11, 2013 at 10:35:54PM +0200, Tobias Burnus wrote:
> >> 
> >> * gfortran's example for random_see should be change to not use 
> >> system_clock for the random seed.
> >
> >I disagree.  The example is just that a short example
> >that demonstrates how to use random_seed.  Anyone using
> >that example in his/her code without testing the results
> >in his/her potentially broken environment should not be
> >programming.
> 
> That is unfair.  Few scientists will know that system clocks are
> an iffy aspect of a programming language, especially as there are
> no fundamental reasons that should be the case.

This has nothing to do with the iffy-ness of system clocks.  My
disagreemnet is predicated on the stupidity of using a 10 line
example subroutine without actually inspecting what it does on 
whatever OS that one chooses to use.  Perhaps, my expectations
for the IQ of scientists is too high.  Are you suggesting that
every code snippet in the manual should contain a cautionary
comment of the form:

! 
! This is only an example.  Use with extreme caution.
!

-- 
Steve

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple



More information about the Cygwin mailing list