On Sat, Dec 01, 2007 at 11:31:55AM +0100, Corinna Vinschen wrote: >On Nov 30 16:36, Christopher Faylor wrote: >> On Fri, Nov 30, 2007 at 03:58:42PM +0100, Corinna Vinschen wrote: >> >On Nov 30 07:26, Eric Blake wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> >> Hash: SHA1 >> >> >> >> 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. >> >> But we do have a fairly transparent way of dealing with this problem which >> will allow any ancient apps to continue to work. We used it for the >> transition >> from 32 -> 64 bit file I/O. > >Unfortunately it doesn't work for variables. We can hide the timezone >function, but how do we alias timezone to _timezone in libcygwin.a?
Why do you say that? It should just be a simple aliasing. cgf -- 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/
