[PING^3] RFC [PATCH] BZ#1077902: New API gettimezone

Paul Eggert eggert@cs.ucla.edu
Fri May 30 15:33:00 GMT 2014


P J P wrote:
>> things alone.
>     Did you even look at the patch? It does not change any API, but introduces a new one.

Yes, of course I looked at the patch.  It would change the glibc API in 
an upwards compatible way.  As I wrote, this would require applications 
to change if they want to use the new facility.  That is not "leaving 
things alone".  As already discussed, applications already have a way to 
solve the problem, one that is widely used and portable: they can set TZ 
to "UTC0" (or to whatever other value they like).  We can therefore 
leave things alone; there's no need for an extension.

> It'll greatly help to discuss whether 'best fit' is the TZ string at the end of the tzdata file, when it is present, or any other line from the tzdata file.

Again, we are going around in circles.  The 'best fit' is not the TZ 
string at the end of the tzdata file.  It is not any other line from the 
tzdata file.  It is not in the tzdata file anywhere.  You are asking for 
something that does not exist.



More information about the Libc-alpha mailing list