DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=VdKusBy+ZRKV4zgE1qUR3xGmYWInny1ZJEAx5efIRvV
	Gp05+Td7huES6f3TQ2A+2DlsPpPbfp/BPT37eNjy6FhKeAZrpuVfBefdNovyuOFf
	5SEjwRfI7b70zOT3WW51VhmoxX2NRjY2bVwSNDeVNeno39kRs0J7c9UM7qU+dyaI
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <5167436C.6060301@cs.utoronto.ca>
Date: Thu, 11 Apr 2013 19:12:44 -0400
From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Cygwin with clock_gettime and CLOCK_MONOTONIC - gives always 0
References: <5166A0B3.70801@net-b.de> <5166BCA1.5040204@net-b.de> <20130411134835.GD18333@calimero.vinschen.de> <51670B6B.3000503@net-b.de> <20130411195200.GJ18333@calimero.vinschen.de> <51671EAA.8030901@net-b.de> <20130411213934.GA30487@troutmask.apl.washington.edu> <Prayer.1.3.5.1304112323420.8772@hermes-2.csi.cam.ac.uk> <20130411230041.GA30988@troutmask.apl.washington.edu>
In-Reply-To: <20130411230041.GA30988@troutmask.apl.washington.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 11/04/2013 7:00 PM, Steve Kargl wrote:
> 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.
> !
This has wandered off topic into some pretty snitty territory... truce?


--
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