Implicit string cast with potential data loss from '%s' to '%s' (IMPLICIT_STRING_CAST_LOSS)Įxplicit string cast from '%s' to '%s' (EXPLICIT_STRING_CAST)Įxplicit string cast with potential data loss from '%s' to '%s' (EXPLICIT_STRING_CAST_LOSS) Implicit string cast from '%s' to '%s' (IMPLICIT_STRING_CAST) When you convert an application to Unicode, you should enable warnings 10 to find problem areas in your code. The Delphi compiler has warnings related to errors in casting types (such as from UnicodeString or WideString down to AnsiString or AnsiChar). However, if a procedure performs operations that are dependent upon the internal structure of the string data or that interact with external libraries, it might be necessary to have separate code paths for UnicodeString and AnsiString. For most code that performs standard string operations, it should not be necessary to have separate UnicodeString and AnsiString code sections. This can be used to maintain code that supports older versions of Delphi and C++Builder in the same source.

In addition, code that writes to or reads from persistent storage needs to ensure that the correct number of bytes are being written or read, since a character might no longer be able to be represented as a single byte.įlags have been provided so that you determine whether string is UnicodeString or AnsiString. The two assumptions listed here first are not true for Unicode, because for Unicode SizeOf(Char) is greater than 1 byte, and the Length of a string is half the number of bytes. Writes and reads strings to or from persistent storage.Directly manipulates strings or PChars.Assumes that the Length of a string is equal to the number of bytes in the string.Setting Up Your Environment for Migrating to Unicode

2.14 Use of PChar Casts to Enable Pointer Arithmetic.

2.5 Calls to Write/WriteBuffer Methods of TStream.

2.4 Calls to Read/ReadBuffer Methods of TStream.

2 Specific Areas to Examine in the Code.1 Setting Up Your Environment for Migrating to Unicode.

Getwindowtext delphi