[date_time] Trac 13194 - %e posix time_input_facet specifier behavior
https://svn.boost.org/trac10/ticket/13194 Just looking at this one, and looking at the documentation, it states that %e is the same as %d however when the value is less than 10, a leading space is to be used instead of a leading zero. The example in the description has a flaw, I believe, and I commented on that. Do folks agree with my comment? Should parsing fail if it says "December 5" (with one space) and the format string is "%B %e"? Valid input would be "December 5" (with two spaces). I also found that the code blindly ignores delimiter specifiers, so I opened a github issue for it: https://github.com/boostorg/date_time/issues/53. Comments appreciated there as well. Thanks, Jim
On 12/21/2017 12:54 PM, James E. King, III via Boost wrote:
https://svn.boost.org/trac10/ticket/13194
Just looking at this one, and looking at the documentation, it states that %e is the same as %d however when the value is less than 10, a leading space is to be used instead of a leading zero.
The example in the description has a flaw, I believe, and I commented on that. Do folks agree with my comment? Should parsing fail if it says "December 5" (with one space) and the format string is "%B %e"? Valid input would be "December 5" (with two spaces).
I think the leading space being used rather than a leading 0 refers to output. On input I would expect spaces to be ignored when parsing.
I also found that the code blindly ignores delimiter specifiers, so I opened a github issue for it: https://github.com/boostorg/date_time/issues/53. Comments appreciated there as well.
Thanks,
Jim
On Thu, Dec 21, 2017 at 2:40 PM, Edward Diener via Boost < boost@lists.boost.org> wrote:
On 12/21/2017 12:54 PM, James E. King, III via Boost wrote:
https://svn.boost.org/trac10/ticket/13194
Just looking at this one, and looking at the documentation, it states that %e is the same as %d however when the value is less than 10, a leading space is to be used instead of a leading zero.
The example in the description has a flaw, I believe, and I commented on that. Do folks agree with my comment? Should parsing fail if it says "December 5" (with one space) and the format string is "%B %e"? Valid input would be "December 5" (with two spaces).
I think the leading space being used rather than a leading 0 refers to output. On input I would expect spaces to be ignored when parsing.
Thanks, the behavior is not specified well in the documentation relative to this behavior. It does say that %e input processing is supported, but locale-specific, so this is still a bug that can be fixed, and the patch in the trac issue looks like it takes care of it. - Jim
participants (2)
-
Edward Diener -
James E. King, III