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: <200203251251.g2PCpYe16580@dymwsm15.mailwatch.com>
From: "Fleischer, Karsten (K.)" <kfleisc1 AT getrag-ford DOT com>
To: "'Wu Yongwei'" <adah AT sh163 DOT net>,
   "'cygwin AT cygwin DOT com'"	 <cygwin AT cygwin DOT com>
Subject: RE: cygwin1.dll bug in ftime
Date: Mon, 25 Mar 2002 07:50:59 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.15)
Content-Type: text/plain;	charset="iso-8859-1"
HOP-COUNT: 1
X-MAILWATCH-INSTANCEID: 01020007ef259d59-4b52-4d5e-ac1d-24172b4b4a3b
X-OriginalArrivalTime: 25 Mar 2002 12:51:34.0139 (UTC) FILETIME=[CB22C4B0:01C1D3FB]

> Also notes the usage of "unspecified". "Unspecified" means 
> the standard does
> not say anything about the implementation, and, IMHO, the 
> implementors are
> free to choose the best practices. 

... or to not implement anything at all.

> I think it is obviously a 
> good way to
> follow BSD.

Possibly.
The better way for application developers is to follow the Single UNIX Specification.
Any application relying on results that are explicitely marked as "unspecified" in the SUS standard can be considered non-portable.

From the SUSv3 documentation:

APPLICATION USAGE
For applications portability, the time() function should be used to determine the current time instead of ftime().

Karsten

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/