4 Feb
2014
4 Feb
'14
1:56 p.m.
On 04-02-2014 10:40, Sebastian Theophil wrote:
On 2014-02-03 16:03, Roland Bock wrote: In most usecases I encountered so far, it is totally OK to interpret NULL values like default values, e.g. NULL strings and empty strings, or NULL foreign keys or 0LL. For those usecases it would be quite annoying to have to check if there really is a value, or always use get_optional_value_or...
Hi Roland,
while I can very well imagine that these "use-cases" exist, I would not like the library to make this the default. I think using boost::optional is the canonical solution that is also impossible to misinterpret.
+ 1. -Thorsten