[fpc-devel] RawByteString Insert etc.

Hans-Peter Diettrich DrDiettrich1 at aol.com
Fri Dec 5 10:51:36 CET 2014

IMO the Insert procedure should change the encoding of the 
string-to-insert into the CP of the target string. Else the target 
string can become unusable, containing an mix of characters from 
different codepages. While a RawByteString can have any encoding, it 
cannot have two encodings at the same time.

BTW, the documentation should be updated to RawByteString arguments.

More candidates:
Concat (implemented where? operator +=?)
Pos (make SubStr CP match Source CP)

To be converted to RawByteString at all (overload?):
Format (?)
LastDelimiter, IsDelimiter (in case of non-ASCII delimiters?)

Should I supply patches?


More information about the fpc-devel mailing list