This is the mail archive of the
mailing list for the glibc project.
Re: [PING^3] RFC [PATCH] BZ#1077902: New API gettimezone
- From: Paul Eggert <eggert at cs dot ucla dot edu>
- To: OndÅej BÃlka <neleai at seznam dot cz>
- Cc: 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: Wed, 28 May 2014 07:34:40 -0700
- Subject: Re: [PING^3] RFC [PATCH] BZ#1077902: New API gettimezone
- Authentication-results: sourceware.org; auth=none
- References: <5361F22E dot 3070206 at redhat dot com> <53628A02 dot 9080702 at cs dot ucla dot edu> <53629388 dot 1060301 at redhat dot com> <53630B0C dot 1050305 at cs dot ucla dot edu> <53633A37 dot 7060405 at redhat dot com> <5363E223 dot 7060303 at cs dot ucla dot edu> <1399061963 dot 56150 dot YahooMailNeo at web192404 dot mail dot sg3 dot yahoo dot com> <1401211363 dot 50264 dot YahooMailNeo at web192402 dot mail dot sg3 dot yahoo dot com> <20140527180827 dot GA25042 at domone dot podge> <538533EB dot 3000501 at cs dot ucla dot edu> <20140528085726 dot GA975 at domone dot podge>
No its same api. You just define timezone_t as char * so you do not have
to implement anything difficult.
But you'd still to make copies of the strings that the char * pointers
point at, no?
Also, this sounds reallllly slow -- perhaps a reasonable
proof-of-API-concept, but not reasonable as an actual change one would
want to make to glibc.
Idea is to have an API which will return the 'best fit' value for the TZ variable
"best fit" is application-dependent. glibc is not in a position to
decide what the best fit is for a particular application.
Plus, "best fit" is a weird thing to ask for. Why would an application
want an approximation to the TZ setting? Why wouldn't it want the real