On Fri, 30 Nov 2007, Corinna Vinschen wrote: > On Nov 30 07:26, Eric Blake wrote: > > According to Corinna Vinschen on 11/30/2007 7:20 AM: > > > > > > However, this *is* a problem in the newlib/cygwin headers. Cygwin > > > exports a timezone function and a _timezone variable. The timezone > > > function was an ill-advised invention in Cygwin way back in the last > > > century. Unfortunately it has to be kept for backward compatibility. > > > > For 1.5.x, yes. But can we delete timezone() for 1.7.x, on the grounds > > that any binary that still uses the timezone function is old enough that > > it would benefit from re-porting to the latest cygwin sources anyway? > > I'm thinking along the same lines. While that breaks backward > compatibility, I'm not overly concerned in case of applications which > have never been ported to a newer Cygwin version the last 10 or so > years.
And plus, renaming the function to, e.g., _cygwin_timezone will allow for a one-line fix for those applications... Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ [EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Belief can be manipulated. Only knowledge is dangerous. -- Frank Herbert -- 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/