Thanks for responding @Geoff_Perlman.
I find myself in a bind here as I have a product I thought was close to release but now find it has deep flaws due to
String's mis-handling of characters. The “easiest” solution is to change every reference in my project for
Text since that will solve the issues but then I will have a product using a deprecated language feature which feels wrong and risky.
Adding a bunch of extensions to
String could work but I have no doubt that the performance will really suffer since they won’t be as fast as the native
Text data type. One of this product’s selling features is its speed so I’m acutely sensitive to performance.
No offence intended but waiting on Xojo to implement a feature request doesn’t seem a viable option as there are no guarantees on turnaround time for implementation.
String exist beside each other? If the concern is that there is a risk of confusion to customers then I think that is the status quo. Those who need to manipulate bytes, are constrained by performance or know they will only be using common unicode characters can use
String. For those who need 100% coverage of the entire language spectrum can use