This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: cygwin1.dll bug in ftime


Thank you for your suggestions. The points are:

1) Cygwin did very well, but not now;

2) I was not using ftime to get time, but to get timezone information.

3) timezone variable is not usable in Cygwin.

So timezone is now not portable. Cygwin broke some "unportable" code.

Best regards,

Wu Yongwei

"Fleischer, Karsten (K.)" wrote:
> 
> > 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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]