Opened 22 years ago
Closed 13 years ago
#922 closed Feature Requests (fixed)
Lexical cast and wide characters
Reported by: | brey | Owned by: | nasonov |
---|---|---|---|
Milestone: | Component: | lexical_cast | |
Version: | None | Severity: | Optimization |
Keywords: | Cc: | kevlin@… |
Description (last modified by )
It would be nice to make lexical_cast be handle to translate through means other than a char-width string. One way to address this is follows: template<typename Target, typename Source, typename E = char> Target lexical_cast(Source arg) { std::basic_stringstream<E> interpreter; ... Other options, such as using traits to try to deduce E from the target type automatically, would be fine, too. Think of the above suggestion as a starting point; however, it would plug what it currently a hole. This feature request is derived from: http://groups.yahoo.com/group/boost/message/10937
Change History (6)
comment:1 by , 15 years ago
Cc: | added |
---|---|
Description: | modified (diff) |
Severity: | → Showstopper |
comment:2 by , 15 years ago
Component: | None → lexical_cast |
---|---|
Severity: | Showstopper → Optimization |
comment:3 by , 15 years ago
Owner: | changed from | to
---|---|
Status: | assigned → new |
comment:4 by , 13 years ago
Resolution: | None → fixed |
---|---|
Status: | new → closed |
It would be nice to make lexical_cast be handle to
translate through means other than a char-width string. lexical_cast supports wchar_t.
Other options, such as using traits to try to deduce E
from the target type automatically, would be fine, too. lexical_cast deduces E from both target and source types.
comment:5 by , 13 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:6 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
(closing it properly this time, unanonymously and with a better formatting)
It would be nice to make lexical_cast be handle to translate through means other than a char-width string.
lexical_cast supports wchar_t.
Other options, such as using traits to try to deduce E from the target type automatically, would be fine, too.
lexical_cast deduces E from both target and source types.
Can't reassign this to Kevlin until he enters his email as described at TicketWorkflow