Re: [fpc-devel] Encoded AnsiString

2013-12-30 Thread Hans-Peter Diettrich
Paul Ishenin schrieb: 30.12.2013 9:07, Hans-Peter Diettrich пишет: Do you think that FPC should really reproduce all this inconsistent behaviour? Who would test or even specify the compatible behaviour, when every new variation will result in more unexpected results? IMO it's much easier to

Re: [fpc-devel] Encoded AnsiString

2013-12-30 Thread Michael Van Canneyt
On Mon, 30 Dec 2013, Paul Ishenin wrote: 30.12.2013 9:07, Hans-Peter Diettrich пишет: Do you think that FPC should really reproduce all this inconsistent behaviour? Who would test or even specify the compatible behaviour, when every new variation will result in more unexpected results? IMO

Re: [fpc-devel] Encoded AnsiString

2013-12-30 Thread Jy V
On Sun, Dec 29, 2013 at 7:26 PM, Hans-Peter Diettrich drdiettri...@aol.comwrote: var a: AnsiString; u: UTF8String; function cpy(s: RawByteString):RawByteString; begin Result := s; end; a := cpy(u); //now a has encoding UTF-8! Here the XE compiler omits the conversion of the RawByteString

Re: [fpc-devel] Encoded AnsiString

2013-12-30 Thread Paul Ishenin
30.12.2013 18:33, Michael Van Canneyt пишет: So how one can help at this stage: 1. Check related FPC tests and write new for the missing cases. 2. Compare FPC and Delphi RTL classes which had beed adjusted in Delphi during the unicodestring move and check whether something minor can be added

Re: [fpc-devel] Encoded AnsiString

2013-12-30 Thread Michael Van Canneyt
On Mon, 30 Dec 2013, Paul Ishenin wrote: 30.12.2013 18:33, Michael Van Canneyt пишет: So how one can help at this stage: 1. Check related FPC tests and write new for the missing cases. 2. Compare FPC and Delphi RTL classes which had beed adjusted in Delphi during the unicodestring move

Re: [fpc-devel] Encoded AnsiString

2013-12-30 Thread Paul Ishenin
30.12.2013 20:25, Michael Van Canneyt wrote: But the experiments for ansi/unicode RTL are already in trunk. Do you plan to take them out ? By experiments I ment having 2 (or 1.5) RTL with unicode + ansi classes which we planned to solve using namespaces. What good is having the unicode

Re: [fpc-devel] Encoded AnsiString

2013-12-30 Thread Marco van de Voort
In our previous episode, Paul Ishenin said: I don't think that this is a good idea, it means that e.g. TStrings.SaveToFile() or TFileStream.Create() is still crippled. Better bite the bullet. This is what I wanted to test in feb/march. This will also mean that we will release 2.8 much

Re: [fpc-devel] Encoded AnsiString

2013-12-30 Thread Marco van de Voort
In our previous episode, Michael Van Canneyt said: But the experiments for ansi/unicode RTL are already in trunk. Do you plan to take them out ? and: What good is having the unicode string support if none of the classes or units make use of it ? Limited. But 2.8.x is not all about

Re: [fpc-devel] Encoded AnsiString

2013-12-30 Thread Michael Van Canneyt
On Mon, 30 Dec 2013, Marco van de Voort wrote: In our previous episode, Michael Van Canneyt said: But the experiments for ansi/unicode RTL are already in trunk. Do you plan to take them out ? and: What good is having the unicode string support if none of the classes or units make use of it

Re: [fpc-devel] Encoded AnsiString

2013-12-30 Thread Paul Ishenin
30.12.2013 20:59, Michael Van Canneyt wrote: That was my idea. If it turns out to be really impossible, we can still do as Paul suggests, but if it works, I would attempt to release 2.8 with dotted units. In each case, the ground work will be done in a branch, so as not to irreversibly