| delorie.com/archives/browse.cgi | search |
| Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
| List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
| List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT cygwin DOT com> |
| List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs> |
| Sender: | cygwin-owner AT cygwin DOT com |
| Mail-Followup-To: | cygwin AT cygwin DOT com |
| Delivered-To: | mailing list cygwin AT cygwin DOT com |
| Message-ID: | <20030825074253.3769.qmail@linuxmail.org> |
| MIME-Version: | 1.0 |
| From: | "peter garrone" <pgarrone AT linuxmail DOT org> |
| To: | cygwin AT cygwin DOT com |
| Date: | Mon, 25 Aug 2003 15:42:52 +0800 |
| Subject: | pthread_cond_timedwait accurate to one second only |
| X-Originating-Ip: | 192.10.200.223 |
| X-Originating-Server: | ws5-2.us4.outblaze.com |
Hi. I would like to use this function down to 10 milliseconds accuracy if possible. However upon looking at winsup/cygwin/thread.cc, it uses the function "ftime" and the millisecond field is ignored. All the examples in the winsup testsuite also generally check to 5 seconds only. Is there any inherent reason why finer timing would not work? -- ______________________________________________ http://www.linuxmail.org/ Now with e-mail forwarding for only US$5.95/yr Powered by Outblaze -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |