On Thu, Feb 25, 2016 at 9:11 PM, silvioprog wrote:
> Well, the problem persists, and I can't understand why this attached
> project works only if compiled with Delphi. The results:
>
> Delphi:
>
> Length: 3
> aañ
>
> FPC:
>
> Length: 5
> aA£A±
>
> Lazarus 1.6 r51630 FPC 3.0.0 i386-win32-win32/win
On Thu, Feb 25, 2016 at 3:47 PM, Jonas Maebe
wrote:
> On 25/02/16 19:31, silvioprog wrote:
>
> So, is the FPC StrMove() function compatible with the Delphi one?
>
> This has nothing to do with StrMove, since clearly the original string is
> already different. If you compile your source code in D
On Thu, Feb 25, 2016 at 4:28 PM, silvioprog wrote:
> On Thu, Feb 25, 2016 at 3:47 PM, Jonas Maebe
> wrote:
>
>> On 25/02/16 19:31, silvioprog wrote:
>>
>> So, is the FPC StrMove() function compatible with the Delphi one?
>>
>> This has nothing to do with StrMove, since clearly the original stri
On 25/02/16 19:31, silvioprog wrote:
So, is the FPC StrMove() function compatible with the Delphi one?
This has nothing to do with StrMove, since clearly the original string
is already different. If you compile your source code in Delphi with
--codepage=65001, it should give the same result a
Hello,
I want to use the StrMove() function in a unit compilable in Delphi (XE)
and FPC, but I don't know why it doesn't work on FPC.
Consider the following code:
{$IFDEF FPC}
{$codepage utf8} // I need to keep my unit in UTF-8
{$ENDIF}
var
a: AnsiString;
la: Integer;
pa: PAnsiChar;
b:
