On 27 Jun 2007, at 23:27, Felipe Monteiro de Carvalho wrote:
before the currently scheduled time
for 2.2.2 (someone said it would be summer 2008, is that right?)
Nobody has said that in this thread afaics, and even if someone did
that would be very unlikely to be right. The only estimates I
On 6/22/07, Jonas Maebe <[EMAIL PROTECTED]> wrote:
Resources patch: up to the Windows maintainers.
And what do the Windows maintainers say?
Considering that lazarus snapshots are now build with a patched fpc
2.1.5 (Vincent, correct me if I am wrong), and it is working fine
here, maybe this cou
En/na Vincent Snijders ha escrit:
On Wed, 27 Jun 2007 19:38:03 +0200
Luca Olivetti <[EMAIL PROTECTED]> wrote:
En/na Luca Olivetti ha escrit:
En/na Cesar Romero ha escrit:
Where S is initialized?
I only see L initialized.
[]s
Cesar Romero
442: L:=length(s);
443: if L<1 then exit;
444: c
On Wed, 27 Jun 2007 19:38:03 +0200
Luca Olivetti <[EMAIL PROTECTED]> wrote:
> En/na Luca Olivetti ha escrit:
> > En/na Cesar Romero ha escrit:
> >> Where S is initialized?
> >> I only see L initialized.
> >>
> >> []s
> >>
> >>
> >> Cesar Romero
> >>>
> >>> 442: L:=length(s);
> >>> 443: if L<1 th
En/na Luca Olivetti ha escrit:
En/na Cesar Romero ha escrit:
Where S is initialized?
I only see L initialized.
[]s
Cesar Romero
442: L:=length(s);
443: if L<1 then exit;
444: case s[1] of
so I can't see how it could possibly be uninitialized.
nothwithstanding the fact that if length(s
En/na Luca Olivetti ha escrit:
BTW, using the "disassemble" function of gdb sometimes reveals where
the unnamed routine really is, so for the
#3 0x08059bec in ?? ()
No symbol table info available.
"disassemble 0x8059bec" *might* help you invastigating the source of
the problem further.
En/na Vinzent Hoefler ha escrit:
On Tuesday 26 June 2007 17:26, Luca Olivetti wrote:
procedure TButlerPhone.Receive(s: string);
so s is a parameter.
This procedure is called exclusively from
procedure TStatusThread.Receive;
begin
FOwner.Receive(FData)
end;
(FOwner is a TButlerPhone)
whic
On 27 jun 2007, at 08:47, Vinzent Hoefler wrote:
In that case, the refcount of the ansistring you pass isn't
increased,
Meaning that the string will be freed once I leave the routine that
called the constructor?
Yes.
Jonas
___
fpc-pascal mailli
On Wednesday 27 June 2007 07:55, Jonas Maebe wrote:
> On 27 jun 2007, at 08:13, Vinzent Hoefler wrote:
> > There also seemed to be some issues with the reference
> > counting: if I passed a local AnsiString to a thread constructor as
> > argument and left the routine then, this seemed to confuse th
On 27 jun 2007, at 08:13, Vinzent Hoefler wrote:
There also seemed to be some issues with the reference
counting: if I passed a local AnsiString to a thread constructor as
argument and left the routine then, this seemed to confuse the thread
throwing SIGSEGVs occasionally.
Maybe the parameter
On Tuesday 26 June 2007 17:26, Luca Olivetti wrote:
> procedure TButlerPhone.Receive(s: string);
>
> so s is a parameter.
> This procedure is called exclusively from
>
> procedure TStatusThread.Receive;
> begin
>FOwner.Receive(FData)
> end;
>
> (FOwner is a TButlerPhone)
>
> which in turn is c
Is there a define to detect if the compiler supports 1,2 byte sets? I could use
something like {$IFNDEF 2_0}{$IFNDEF 2_1}{$IFNDEF 2_2} but maybe there is a
smarter solution.
Vincnet
- Original Message -
From: 刘治国
To: [EMAIL PROTECTED]
Sent: Wednesday, June 27, 2007 9:57 AM
Subject: l
12 matches
Mail list logo
