On 08/21/2012 11:09 AM, Graeme Geldenhuys wrote:
Can't we just introduce UTF8String and UTF16String types. By the name they clearly state what encoding the hold.
It does make sense to (optionally) provide dynamically encoded strings, so that it is possible to do library functions that work with any encoding (and can be called with any encoding) without the need to do overloaded functions or do conversions under the hood.
-Michael _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
