I wonder how these many messages occur, even in building the libraries.
Is it only lazyness why according fixes are missing, or are there
reasons why such conversions are inevitable?
Dumb question: what's the default "string" type in FPC trunk? When it's
AnsiString, in which situations are UnicodeString conversions really
required, in contrast to pre-UnicodeString versions?
What about WideString? E.g. fcl-xml contains a lot of WideString types -
shouldn't these be replaced by (or retyped into) UnicodeString now? IMO
only the Windows COM libraries require real WideString (BSTR) arguments,
while the ordinary "W" API should be happy with pointers to UnicodeStrings.
DoDi
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
