This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: cygwin1.dll bug in ftime
- 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>
- Date: Mon, 25 Mar 2002 07:50:59 -0500
- Subject: RE: cygwin1.dll bug in ftime
- Hop-count: 1
> 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/