I'm afraid these types are not interconvertible in my practice (ValueTo<> generates exception in many cases).
Here is simplified version of previous code:
CONSOLE_APP_MAIN
{
String s = "11";
int i = ValueTo<int>(StdConvertInt().Scan(s)); //generates exception
}
while this code works:
CONSOLE_APP_MAIN
{
String s = "11";
int i = ValueTo<int64>(StdConvertInt().Scan(s)); //OK!
}
It is just one of many cases (the absence of interconvertibility makes handling Ctrl::GetData() a headache too).
It is because you are making your life hard using ValueTo
Try this:
CONSOLE_APP_MAIN
{
String s = "11";
int i = StdConvertInt().Scan(s);
}
ValueTo is supposed to be used in two cases:
- as part of implementation of RichValue type (type with "full support" - hashcode, equality comparison, direct coversion)
- as a way to extract RawValue type (usually some of your type used to implement something, when you do not bother about RichValue traits, just simply need to pass such type as Value through).
Sorry for incomplete docs. In fact, Value is one of last places without proper documentation - unfortunately it is also one that quite hard to document....
Members
Pages
Help
Register
Login
Home
