public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/114645] std::chrono::current_zone ignores $TZ on Linux Date: Mon, 08 Apr 2024 20:51:22 +0000 [thread overview] Message-ID: <bug-114645-4-OgU8Kfro87@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114645-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114645 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Hristo Venev from comment #4) > Therefore current_zone() as currently implemented is worse than useless -- > it is a footgun. So don't use it then. > The people who wrote the standard probably did not consider how various > platforms handle default time zones this at all. That's a pretty bug assumption, and wrong. > I don't understand why you consider the ability to override the default time > zone using an environment variable to be a flaw. For one, the environment is mutable and not threadsafe. Anyway, this isn't going to change just because you don't like it.
next prev parent reply other threads:[~2024-04-08 20:51 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-08 19:01 [Bug libstdc++/114645] New: " hristo at venev dot name 2024-04-08 19:27 ` [Bug libstdc++/114645] " redi at gcc dot gnu.org 2024-04-08 20:23 ` hristo at venev dot name 2024-04-08 20:25 ` redi at gcc dot gnu.org 2024-04-08 20:46 ` hristo at venev dot name 2024-04-08 20:48 ` redi at gcc dot gnu.org 2024-04-08 20:51 ` redi at gcc dot gnu.org [this message] 2024-04-08 20:56 ` hristo at venev dot name 2024-04-09 9:19 ` redi at gcc dot gnu.org 2024-04-09 9:41 ` hristo at venev dot name 2024-04-09 9:46 ` xry111 at gcc dot gnu.org 2024-04-09 9:49 ` hristo at venev dot name 2024-04-09 16:40 ` redi at gcc dot gnu.org 2024-04-09 17:19 ` hristo at venev dot name 2024-04-09 23:29 ` harald at gigawatt dot nl 2024-04-09 23:29 ` redi at gcc dot gnu.org 2024-04-09 23:43 ` redi at gcc dot gnu.org 2024-04-09 23:47 ` redi at gcc dot gnu.org 2024-04-09 23:50 ` harald at gigawatt dot nl 2024-04-09 23:57 ` redi at gcc dot gnu.org 2024-04-10 0:07 ` redi at gcc dot gnu.org 2024-04-10 0:26 ` harald at gigawatt dot nl 2024-04-10 0:57 ` redi at gcc dot gnu.org 2024-04-10 1:10 ` redi at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-114645-4-OgU8Kfro87@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).