On Tue, Sep 30, 2025 at 10:50 AM Steffen Nurpmeso via tz <[email protected]> wrote: > > Magnus Fromreide via tz wrote in > <[email protected]>: > |On Wed, Sep 24, 2025 at 12:57:49PM -0700, Paul Eggert via tz wrote: > |> On 2025-09-24 10:14, Robert Elz wrote: > |>> Date: Wed, 24 Sep 2025 07:39:27 -0700 > |>> From: Paul Eggert <[email protected]> > |>>| This wording is > |>>| intended to require the 7th Edition Unix behavior, where calling any of > |>>| localtime, gmtime, and ctime overwrote the same struct tm object. > |>> > |>> No it isn't, it is meant to allow that behaviour - no-one with even an > |>> iota of sanity would require things to be implemented that way. > |> > |> If only you could go back to the 1980s and whisper that into Douglas \ > |> Gwyn's > |> ears! > | > |If I could go back and whisper in his ears I would whisper that the output > |buffer should be passed as an argument, that way the _r versions wouldn't \ > |be > |needed and this whole issue would evaporate. > > I would ask for objects, as via tzalloc(), which strives me as the > only truly sane interface: you can implement all others with it. > Paul Eggert wants to port them for about ten years also to their > GNUlib and GNU's libc, but these heavyweights seem to miss them > still. It would surely aid in standard adoption if they came.
yeah, they've been exposed in Android's libc since api level 35, in part because rust folks were unable to build safe tz api on top of the existing api. it's so obviously "what the api _should_ have been" that i broke my usual rule about being the libc that moves first :-) > --End of <[email protected]> > > --steffen > | > |Der Kragenbaer, The moon bear, > |der holt sich munter he cheerfully and one by one > |einen nach dem anderen runter wa.ks himself off > |(By Robert Gernhardt)
