Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: <3C9F21DF.DA6D8C71@sh163.net> Date: Mon, 25 Mar 2002 21:10:55 +0800 From: Wu Yongwei X-Mailer: Mozilla 4.79 [en] (Win95; U) X-Accept-Language: en,en-GB,zh-CN,zh,fr MIME-Version: 1.0 To: "Fleischer, Karsten (K.)" CC: cygwin AT cygwin DOT com Subject: Re: cygwin1.dll bug in ftime References: <200203251251 DOT g2PCpY629291 AT dymwsm12 DOT mailwatch DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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/