|
If you were logged in you would be able to see more operations.
|
|
|
|
Time Tracking:
|
|
Original Estimate:
|
4h
|
|
|
Remaining Estimate:
|
4h
|
|
|
Time Spent:
|
Not Specified
|
|
|
|
| Severity: |
Incorrect Behavior
|
std::time_get<>::get_date() is required to be able to parse the output produced by std::time_put<>::put(..., 'x'). For some locales, the '%x' format specifier expands out to '%e.%m.%Y'. When a date is formatted using this, there will be a leading space, and that leading space causes the time_get<>::get_date() operation to fail.
The root of the problem is that the POSIX strftime() function [which we emulate in time_get] requires that the '%e' specifier generate whitespace for single digit monthdays, and the POSIX strptime() function says that the number may be padded on the left with 0s. It does not appear to specify that whitespace is allowed. The strptime() implementation on some platforms [sun, linux, compaq, aix] allow this whitespace, while others [hp, freebsd] do not.
Discussion here.
http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200708.mbox/%3c46CC8D6C.9000007@roguewave.com%3e
|
|
Description
|
std::time_get<>::get_date() is required to be able to parse the output produced by std::time_put<>::put(..., 'x'). For some locales, the '%x' format specifier expands out to '%e.%m.%Y'. When a date is formatted using this, there will be a leading space, and that leading space causes the time_get<>::get_date() operation to fail.
The root of the problem is that the POSIX strftime() function [which we emulate in time_get] requires that the '%e' specifier generate whitespace for single digit monthdays, and the POSIX strptime() function says that the number may be padded on the left with 0s. It does not appear to specify that whitespace is allowed. The strptime() implementation on some platforms [sun, linux, compaq, aix] allow this whitespace, while others [hp, freebsd] do not.
Discussion here.
http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200708.mbox/%3c46CC8D6C.9000007@roguewave.com%3e |
Show » |
made changes - 06/Sep/07 07:27 PM
| Field |
Original Value |
New Value |
|
Description
|
std::num_get<>::get_date() is required to be able to parse the output produced by std::num_put<>::put(..., 'x'). For some locales, the '%x' format specifier expands out to '%e.%m.%Y'. When a date is formatted using this, there will be a leading space, and that leading space causes the num_get<>::get_date() operation to fail.
The root of the problem is that the POSIX strftime() function requires that the '%e' specifier generate whitespace for single digit monthdays, and the POSIX strptime() function says that the number may be padded on the left with 0s. It does not appear to specify that whitespace is allowed. The strptime() implementation on some platforms [sun, linux, compaq, aix] allow this whitespace, while others [hp, freebsd] do not.
Discussion here.
[http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200708.mbox/%3c46CC8D6C.9000007@roguewave.com%3e]
|
std::time_get<>::get_date() is required to be able to parse the output produced by std::time_put<>::put(..., 'x'). For some locales, the '%x' format specifier expands out to '%e.%m.%Y'. When a date is formatted using this, there will be a leading space, and that leading space causes the time_get<>::get_date() operation to fail.
The root of the problem is that the POSIX strftime() function [which we emulate in time_get] requires that the '%e' specifier generate whitespace for single digit monthdays, and the POSIX strptime() function says that the number may be padded on the left with 0s. It does not appear to specify that whitespace is allowed. The strptime() implementation on some platforms [sun, linux, compaq, aix] allow this whitespace, while others [hp, freebsd] do not.
Discussion here.
[http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200708.mbox/%3c46CC8D6C.9000007@roguewave.com%3e]
|
|
Summary
|
std::num_put can generate output that is not parseable by std::num_get facet
|
std::time_put can generate output that is not parseable by std::time_get facet
|
made changes - 06/Apr/08 10:59 PM
|
Assignee
|
|
Martin Sebor
[ sebor
]
|
|
Severity
|
|
Incorrect Behavior
|
|
Fix Version/s
|
|
4.3
[ 12312692
]
|
|
Remaining Estimate
|
|
4h
[ 14400
]
|
|
Original Estimate
|
|
4h
[ 14400
]
|
|
Bug
Open
Major
std::time_put can generate output that is not parseable by std::time_get facet
