This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
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 thing?
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |