On 02/28/2014 05:06 PM, Sven Barth wrote:
- "non-Raw" does not allow for modifying the type and code-length
fields
Yes, but you can always do it by converting to RawByteString:
Of course but then there is no auto conversion any more.
The start of the discussion was using a type that _both_ allows for
modifying the type and code-length fields _and_at_the_same_time_
provides auto-conversion (e.g.) as the base for TStrings to (e.g.) allow
Lazarus to do an LCL API that (e.g.) works with UTF16 encoded strings on
Windows and with UTF8 encoded strings in Linux without the need to
re-compile the compiler and/or the RTL with different options.
-Michael
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
