This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Cygwin with clock_gettime and CLOCK_MONOTONIC - gives always 0
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: "N.M. Maclaren" <nmm1 at cam dot ac dot uk>
- Cc: cygwin at cygwin dot com, fortran at gcc dot gnu dot org
- Date: Thu, 11 Apr 2013 16:00:41 -0700
- Subject: Re: Cygwin with clock_gettime and CLOCK_MONOTONIC - gives always 0
- References: <5166A0B3 dot 70801 at net-b dot de> <5166BCA1 dot 5040204 at net-b dot de> <20130411134835 dot GD18333 at calimero dot vinschen dot de> <51670B6B dot 3000503 at net-b dot de> <20130411195200 dot GJ18333 at calimero dot vinschen dot de> <51671EAA dot 8030901 at net-b dot de> <20130411213934 dot GA30487 at troutmask dot apl dot washington dot edu> <Prayer dot 1 dot 3 dot 5 dot 1304112323420 dot 8772 at hermes-2 dot csi dot cam dot ac dot uk>
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