This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PING^2] RFC [PATCH] BZ#1077902: New API gettimezone
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Paul Eggert <eggert at cs dot ucla dot edu>, P J P <pj dot pandit at yahoo dot co dot in>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
- Date: Tue, 29 Apr 2014 16:59:38 -0400
- Subject: Re: [PING^2] RFC [PATCH] BZ#1077902: New API gettimezone
- Authentication-results: sourceware.org; auth=none
- References: <1396499286 dot 85118 dot YahooMailNeo at web192405 dot mail dot sg3 dot yahoo dot com> <1397301884 dot 32837 dot YahooMailNeo at web192402 dot mail dot sg3 dot yahoo dot com> <534971E4 dot 6060001 at cs dot ucla dot edu> <53497633 dot 6060804 at redhat dot com> <1397324033 dot 69177 dot YahooMailNeo at web192403 dot mail dot sg3 dot yahoo dot com> <5349A4B0 dot 2070206 at redhat dot com> <1397375798 dot 36419 dot YahooMailNeo at web192401 dot mail dot sg3 dot yahoo dot com> <1397414803 dot 70882 dot YahooMailNeo at web192403 dot mail dot sg3 dot yahoo dot com> <534B8A9F dot 8030806 at redhat dot com> <1397469748 dot 42212 dot YahooMailNeo at web192405 dot mail dot sg3 dot yahoo dot com> <1398146221 dot 72442 dot YahooMailNeo at web192403 dot mail dot sg3 dot yahoo dot com> <1398755742 dot 94004 dot YahooMailNeo at web192405 dot mail dot sg3 dot yahoo dot com> <535F74EE dot 8010002 at redhat dot com> <1398775268 dot 92264 dot YahooMailNeo at web192405 dot mail dot sg3 dot yahoo dot com> <535FC11B dot 3000906 at cs dot ucla dot edu> <535FF1CD dot 1030601 at redhat dot com> <535FFA2E dot 5050005 at cs dot ucla dot edu>
On 04/29/2014 03:14 PM, Paul Eggert wrote:
> On 04/29/2014 11:39 AM, Carlos O'Donell wrote:
>> In that case nothing short of stuffing the zone*into* TZ will
>> help
> And even that could have problems if the API stuffs a
> version-3-format zone into a TZ string that's shipped to a
> destination system that groks only version 2.Presumably the version
> number will be in the string somewhere so the destination could
> report an error, but how would that actually work?
I'll let PJP think about it.
>> Unfortunately all of this complicates the API.
> Yes. This complication is a cost, and the cost/benefit ratio seems
> pretty high here.
I don't feel like we're done hashing it out.
As I said before I'd like to see the unified tzalloc et. al. solution
since it solves the unique problem of tz-specific messages
per-thread and may with a slight enhancement fix this issue.
The implementation is certainly up in the air, but I reserve my
judgement until later.
Cheers,
Carlos.