public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/45896] [C++0x] Facet time_get not reading dates according to the IEEE 1003 standard.
Date: Tue, 05 Oct 2010 18:24:00 -0000 [thread overview]
Message-ID: <20101005182400.f0RtaANoRJPiTLlUY-04wOnIT3nc7leX11Pul8mcSRw@z> (raw)
In-Reply-To: <bug-45896-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45896
Paolo Carlini <paolo.carlini at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
CC| |paolo.carlini at oracle dot
| |com
Component|c++ |libstdc++
--- Comment #4 from Paolo Carlini <paolo.carlini at oracle dot com> 2010-10-05 18:24:44 UTC ---
Actually, adding this sort of flexibility then hits
http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#461. Better
dealing with this as part of a more general review of time_get for C++0x.
next prev parent reply other threads:[~2010-10-05 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 16:11 [Bug c++/45896] New: Facet time_get not reading dates according to the standard alexander.rojas at gmail dot com
2010-10-05 16:46 ` [Bug c++/45896] [C++0x] Facet time_get not reading dates according to the IEEE 1003 standard paolo.carlini at oracle dot com
2010-10-05 17:57 ` paolo.carlini at oracle dot com
2010-10-05 18:24 ` paolo.carlini at oracle dot com [this message]
2021-03-07 16:30 ` [Bug libstdc++/45896] " redi at gcc dot gnu.org
2021-12-10 16:20 ` jakub 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=20101005182400.f0RtaANoRJPiTLlUY-04wOnIT3nc7leX11Pul8mcSRw@z \
--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).