Op 2010-10-21 08:29, Graeme Geldenhuys het geskryf:
>
> Length() returns number of bytes, not number of characters. The incorrect
> assumption was made back in Delphi (before unicode support).
>From Delphi 7 & Kylix 3 help:
"For single-byte and multibyte strings, Length returns the number of byt
Op 2010-10-21 08:17, Felipe Monteiro de Carvalho het geskryf:
> On Thu, Oct 21, 2010 at 1:41 AM, Zaher Dirkey wrote:
>> How to get the real length of WideString variable.
>
> Length in which unit? WideChars (2 bytes each) or Bytes?
>
> Length() returns the amount of WideChars AFAIK
>
Length()
Op 2010-10-20 20:36, Jonas Maebe het geskryf:
>
> On 20 Oct 2010, at 19:54, Brian Winfrey wrote:
>
>>> make OPT="-O-" DEBUG=1 all
>>
>> When I ran this I see that both -dDEBUG and -dRELEASE are passed on
>> the fpc command line. Is that correct?
>
> Yes.
Mind explaining why? DEBUG and RELEASE
On Thu, Oct 21, 2010 at 1:41 AM, Zaher Dirkey wrote:
> How to get the real length of WideString variable.
Length in which unit? WideChars (2 bytes each) or Bytes?
Length() returns the amount of WideChars AFAIK
--
Felipe Monteiro de Carvalho
___
fpc-p
On Thu, Oct 21, 2010 at 2:28 AM, Zaher Dirkey wrote:
> var
> ws: widestring;
> begin
> ws:= 'زاهر';
> Label3.Caption := inttostr(length(ws));
> //= 8
Here the compiler assumes that your source code is encoded in the
default system encoding and then it converts your string to utf-16.
Probabl
On Thu, Oct 21, 2010 at 1:41 AM, Zaher Dirkey wrote:
> How to get the real length of WideString variable.
>
>
Hmm, I think i found my problem but not understand it, i used Lazarus as
editor to write the code
var
ws: widestring;
begin
ws:= 'زاهر';
Label3.Caption := inttostr(length(ws));
//=
How to get the real length of WideString variable.
Thanks in advance.
--
Zaher Dirkey
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
On 20 Oct 2010, at 19:54, Brian Winfrey wrote:
>> make OPT="-O-" DEBUG=1 all
>
> When I ran this I see that both -dDEBUG and -dRELEASE are passed on
> the fpc command line. Is that correct?
Yes.
Jonas
___
fpc-pascal maillist - fpc-pascal@lists.fr
Yes. It's what I saw. I was still able to trace database components
line by line using Lazarus and GDB though.
On Wed, Oct 20, 2010 at 12:54 PM, Brian Winfrey wrote:
>> make OPT="-O-" DEBUG=1 all
>
> When I ran this I see that both -dDEBUG and -dRELEASE are passed on
> the fpc command line. Is
> make OPT="-O-" DEBUG=1 all
When I ran this I see that both -dDEBUG and -dRELEASE are passed on
the fpc command line. Is that correct?
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
On Tue, 19 Oct 2010 21:18:03 +0100
Vannus wrote:
> your example is at the start of a "for loop" block, which is much the same
> as having it at the start of a procedure block
So much the same that you can do it in pascal?
What about variables declared inside this for loop or inside the else block
On Wed, 20 Oct 2010, John wrote:
Hi all,
Does anyone know if TBuFDataset.Locate honours the TLocateOptions parameter
passed to it ? It certainly doesn't *seem* to work.
I am actually using a TSQLQuery against an SQLite3 database, Laz 0.9.28.2, fpc
2.2.4, Win32.
I should say that I am pr
12 matches
Mail list logo
