Steven Watanabe wrote:
AMDG
Andrey Semashev wrote:
My current vision is that Boost.NumericConversion and Boost.Units will provide a support layer for Boost.Convert (let's call it that way for now). That support layer will be implemented as a regular extension for the Boost.Convert library. So, the "convert" function will eventually call numeric_cast or quantity_cast, or any other appropriate tool in these libraries to fulfill the conversion.
There is no function called quantity_cast, in the released version of Boost.Units--it's spelled static_cast.
Huh? I can see it in the library docs: http://tinyurl.com/adkdd7
The problem with a fully generic convert is that it's a different beast from string conversions. Converting to and from a string can require formatting information that is meaningless for other conversions and which cannot easily be provided by fully generic code.
This is where tools like Boost.Parameter could come forward. String-related conversions may not be the only domain where passing arbitrary parameters to the conversion mechanism is desirable.