Georg Baum schrieb:
Currently we are doing something illegal if iconv fails (creating a vector from two pointers, where the end is before the start). That throws a std::bad_alloc exception in my environment. What do we want to do? The attached patch simply returns an empty string, but I am not sure whether that is what we want. We could also throw an exception and handle that in the caller. What do others think?
For what reason may iconv fail? Doesn't this indicate an internal error?

How about adding assertion?

Michael

Reply via email to