From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,8ee4430d1820a774
X-Google-Attributes: gid103376,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news2.google.com!news.glorb.com!peer1.news.newnet.co.uk!194.159.246.34.MISMATCH!peer-uk.news.demon.net!kibo.news.demon.net!news.demon.co.uk!demon!not-for-mail
From: Simon Wright <simon.j.wright@mac.com>
Newsgroups: comp.lang.ada
Subject: Re: GNAT.Sockets: Timeval_Duration is in milliseconds?
Date: Thu, 13 Dec 2007 13:13:56 +0000
Organization: Pushface
Message-ID: <m28x3yhh4b.fsf@mac.com>
References: 
 <9d687056-c98b-405a-b166-afddac34f109@e67g2000hsc.googlegroups.com>
 <m2fxycj0pm.fsf@mac.com>
 <99906a58-2645-4880-bd13-9b63a30ffb59@e4g2000hsg.googlegroups.com>
 <m2bq8ziv1z.fsf@mac.com>
 <8808f9fb-64a5-4a44-9684-dc0446a26bbc@b1g2000pra.googlegroups.com>
 <m2y7c3h482.fsf@mac.com>
 <ffe83e08-568a-417d-bae0-f8a1b71a25fa@w56g2000hsf.googlegroups.com>
 <m2tzmqgvqa.fsf@mac.com>
 <8934100e-0576-4078-8e15-cc4aa942af3f@e6g2000prf.googlegroups.com>
 <m2hcipgeep.fsf@mac.com>
 <9de762a3-bac6-4295-b321-3e8091baf28d@d27g2000prf.googlegroups.com>
NNTP-Posting-Host: pogner.demon.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: news.demon.co.uk 1197551637 26456 62.49.19.209 (13 Dec 2007 13:13:57
 GMT)
X-Complaints-To: abuse@demon.net
NNTP-Posting-Date: Thu, 13 Dec 2007 13:13:57 +0000 (UTC)
Cancel-Lock: sha1:gpAPAumY0PzFglFhyHJAEhJdQ2w=
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (darwin)
Xref: g2news1.google.com comp.lang.ada:18918
Date: 2007-12-13T13:13:56+00:00
List-Id: <comp.lang.ada>

gpriv@axonx.com writes:

> On Dec 11, 3:33 pm, Simon Wright <simon.j.wri...@mac.com> wrote:
>> gp...@axonx.com writes:
>> > Yep, it worked:
>>
>> > ..done with EXPIRED after  4.999302724
>>
>> So GNAT GPL 2007 handles _this_ call right -- which functionality was
>> it you had the problem with? Do you have a test case?
>
>
> Linux update:
>
> Timeout value is in seconds here. So it is only a Windows problem as
> to be expected.

Looking at http://msdn2.microsoft.com/en-us/library/ms740141.aspx it
turns out that the Windows version of select(2) uses a struct timeval*
-- so not surprising that it behaves as we were expecting. Huh.

--S