public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/77760] get_time needs to set tm_wday amd tm_yday
Date: Wed, 15 Dec 2021 19:43:46 +0000 [thread overview]
Message-ID: <bug-77760-4-eGK4YcFlSf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-77760-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77760
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Can we have any state passed around?
_M_extract_via_format can have some extra reference argument to some state like
glibc has passed through it, but wouldn't that work only for the recursive
calls?
E.g. if one uses get with "%r" format or some other one that recurses and
contains everything to recompute the fields, we could recompute them.
But if get itself contains a format string, then each format specifier in it
seems to be required to be processed separately by
https://eel.is/c++draft/locale.time.get#members-8.4
- a virtual method which has standard mandated arguments is called for each
format specifier, so it is unclear how to carry some state around the parsing
of the whole format string.
next parent reply other threads:[~2021-12-15 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-77760-4@http.gcc.gnu.org/bugzilla/>
2021-12-15 19:43 ` jakub at gcc dot gnu.org [this message]
2022-01-10 14:40 ` cvs-commit at gcc dot gnu.org
2023-02-09 8:50 ` aoliva at gcc dot gnu.org
2023-02-09 9:08 ` jakub at gcc dot gnu.org
2023-02-09 23:40 ` aoliva at gcc dot gnu.org
2023-02-10 3:05 ` redi at gcc dot gnu.org
2023-02-10 8:33 ` jakub at gcc dot gnu.org
2023-02-17 7:54 ` aoliva 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-77760-4-eGK4YcFlSf@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: link
Be 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).