New behaviour: Such type casts now always give a compile time error.Old behaviour: It was possible to typecast ordinal constants into records/sets/arrays at compile time.Typecasting ordinal constants to complex types (records, arrays, sets) Remedy: If you do not want any translation to be performed, add an additional type conversion to an integer type in between, e.g.Effect: If you previously typecasted chars to widechars or the other way around (possibly via parameter passing or assignments), these type conversions will now cause the data to be translated.Reason: Bug report 7758, and consistency with conversions between shortstrings/ansistrings and widestrings.
#Free pascal crt unit download code#
Example: char_var:=char(widechar_var) used to put the lower 8 bits of widechar_var into char_var, while now the widestring manager is called to translate widechar_var from UTF-16 to the active code page.If a converted widechar is not representable in a single char, the result of the conversion is always '?' New behaviour: A char to a widechar conversion or vice versa now triggers the widestring manager, and converts the data from ansichar to widechar or the other way around.Old behaviour: Type conversions between chars and widechars did not cause any translations of the data.*Win32(Windows 95, 98, ME, NT, 2000, XP, 2003) (~21 Mb)_ Ĭhar to WideChar conversions and vice versa
0 kommentar(er)
