Am Freitag, den 01.09.2006, 11:50 +0200 schrieb Michael Van Canneyt:
>
> On Fri, 1 Sep 2006, Carsten Bager wrote:
>
> >> Hi,
> >>
> >> sorry, I cannot answer your question, but may I as:
> >>
> >>
> >> Am Donnerstag, den 31.08.2006, 13:13 +0200 schrieb Carsten Bager:
> >>
> >>> I am using the com
>
> On 31 aug 2006, at 13:13, Carsten Bager wrote:
>
> > Here is 2 examples of how the fpc compiler dos when comparing a
> > string constant with a pchar . The first is compiled with the 204
> > compiler and second one is compiled with the 202 compiler.
>
> The reason we now favour ansistring of
On 31 aug 2006, at 13:13, Carsten Bager wrote:
Here is 2 examples of how the fpc compiler dos when comparing a
string constant with a pchar . The first is compiled with the 204
compiler and second one is compiled with the 202 compiler.
The reason we now favour ansistring of shortstring in cas
On Fri, 1 Sep 2006, Carsten Bager wrote:
Hi,
sorry, I cannot answer your question, but may I as:
Am Donnerstag, den 31.08.2006, 13:13 +0200 schrieb Carsten Bager:
I am using the compiler on an embedded Arm 7 platform and Ansi
strings is not an option.
How can you do this?
The 2.0.2 su
> Hi,
>
> sorry, I cannot answer your question, but may I as:
>
>
> Am Donnerstag, den 31.08.2006, 13:13 +0200 schrieb Carsten Bager:
>
> > I am using the compiler on an embedded Arm 7 platform and Ansi
> > strings is not an option.
>
> How can you do this?
The 2.0.2 supports the ARM proces
Here is 2 examples of how the fpc compiler dos when comparing a
string constant with a pchar . The first is compiled with the 204
compiler and second one is compiled with the 202 compiler.
I am using the compiler on an embedded Arm 7 platform and Ansi
strings is not an option.
I want to force the 2
