Am 11.05.2016 19:35 schrieb "Santiago A." <s...@ciberpiula.net>: > Something about codpages needs a second thought. > > a) There shouldn't be automatic conversion at all. > b) The codepage of a string shouldn't change when you assign a string with another codepage, just rise an error. > c) Corollary of previous premises: Empty strings should also have codepage.
The codepage aware ansistring was implemented for Delphi-compatibility so this is highly unlikely to change. > Extra 1) Beside calling SetSetcodepage, it would be handy that you could set the codepage when you declare a string. I don't mean codepage should be statically typed, just it would be handy. A string is Nil upon it's declaration so there is nowhere where you could store that information. It only has the static codepage that it had been declared with. > Extra 2) Being able to set the codepage statically, so that mismatch codepage could be detected in compiler time, would be handy. In this case I do mean codepage could also be statically typed, Codepages are already set statically. Regards, Sven
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
