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 c++/45896] [C++0x] Facet time_get not reading dates according to the IEEE 1003 standard.
Date: Tue, 05 Oct 2010 16:46:00 -0000 [thread overview]
Message-ID: <20101005164600.9ZKwpEOgUKuqC2-qPGzcBP02lzQbtueVd42tbUDxXSo@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
----------------------------------------------------------------------------
Priority|P3 |P4
Summary|Facet time_get not reading |[C++0x] Facet time_get not
|dates according to the |reading dates according to
|standard. |the IEEE 1003 standard.
Severity|normal |enhancement
--- Comment #2 from Paolo Carlini <paolo.carlini at oracle dot com> 2010-10-05 16:46:41 UTC ---
I suppose you are referring to the sentences "leading zeros shall be permitted
but shall not be required", right? Because they do *not* exist in the C(99) ISO
Standard, which is the normative reference for C++98, in this area. In general,
ISO 8601, in turn, is pretty strict about those formats.
Only C++0x references explicitly "the ISO/IEC 9945 function strptime" (ISO/IEC
9945 is the same as IEEE 1003), which is more flexible about leading zeros.
Thus, C++0x work, in due course...
next prev parent reply other threads:[~2010-10-05 16:46 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 ` paolo.carlini at oracle dot com [this message]
2010-10-05 17:57 ` [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 18:24 ` [Bug libstdc++/45896] " paolo.carlini at oracle dot com
2021-03-07 16:30 ` 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=20101005164600.9ZKwpEOgUKuqC2-qPGzcBP02lzQbtueVd42tbUDxXSo@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).