On 2011-12-02 at 12:58:10 [+0100], Michael Bridgers <mibrid@xxxxxxx> wrote: > I want to make it very clear that these changes will be backwardly > compatible. Of course, by its definition, there will be changes to the > behavior of the BString. But for current operations that maintain a > valid UTF-8 string, the behavior will not change. The behavior will only > be different when the operation would have created an invalid UTF-8 > string. Plus, I will add enhanced operations to the class. A behavioral change like this is a problem for backward compatibility. Be did not document BString to be able to hold only valid UTF-8 strings, but any valid C-String. So a behavioral change in this respect might break things. CU, Ingo