On 09/06/10 15:50, Marcos Douglas wrote:
On Tue, Jun 8, 2010 at 3:44 PM, Luiz Americo Pereira Camara
wrote:
Marcos Douglas escreveu:
Exactly.
Therefore I always used 'const' only at 'strings' params. I thought it
had changed, but not. ;-)
It can be useful for record parame
On Tue, Jun 8, 2010 at 3:44 PM, Luiz Americo Pereira Camara
wrote:
> Marcos Douglas escreveu:
>> Exactly.
>> Therefore I always used 'const' only at 'strings' params. I thought it
>> had changed, but not. ;-)
>
> It can be useful for record parameters also
>
If the record have strings, I think.
Marcos Douglas escreveu:
On Tue, Jun 8, 2010 at 12:55 PM, Luiz Americo Pereira Camara
wrote:
Marcos Douglas escreveu:
Hi Luiz,
On Mon, Jun 7, 2010 at 10:35 PM, Luiz Americo Pereira Camara
wrote:
Take a look at
http://lazarusroad.blogspot.com/2008/11/effect-of-using-constant
On Tue, Jun 8, 2010 at 12:55 PM, Luiz Americo Pereira Camara
wrote:
> Marcos Douglas escreveu:
>>
>> Hi Luiz,
>>
>> On Mon, Jun 7, 2010 at 10:35 PM, Luiz Americo Pereira Camara
>> wrote:
>>
>>>
>>> Take a look at
>>>
>>> http://lazarusroad.blogspot.com/2008/11/effect-of-using-constant-parameter-f
Marcos Douglas escreveu:
Hi Luiz,
On Mon, Jun 7, 2010 at 10:35 PM, Luiz Americo Pereira Camara
wrote:
Take a look at
http://lazarusroad.blogspot.com/2008/11/effect-of-using-constant-parameter-for.html
Then, this continue true how I said in other mail:
On Mon, Jun 7, 2010 at 11:59 A
Hi Luiz,
On Mon, Jun 7, 2010 at 10:35 PM, Luiz Americo Pereira Camara
wrote:
>
> Take a look at
> http://lazarusroad.blogspot.com/2008/11/effect-of-using-constant-parameter-for.html
>
Then, this continue true how I said in other mail:
On Mon, Jun 7, 2010 at 11:59 AM, Marcos Douglas wrote:
> Al
Marcos Douglas escreveu:
Well... just to I will know. A long time ago (Delphi 4) I learned:
Always use 'const' for 'strings' because this is faster. Strings will
be passed by reference. This remains true?
eg:
var str: string;
procedure Foo1(const s: string);
procedure Foo2(s: string);
Ta
On 03 Jun 2010, at 00:02, José Mejuto wrote:
Any idea
about how to debug the reason of the sudden stop ?
You can try putting breakpoints on FPEXIT, _haltproc and _exit (the
last one only exists if libc is linked, but that's definitely the case
here; note that all of them are case-sensitiv
On 03 Jun 2010, at 10:08, Jonas Maebe wrote:
On 03 Jun 2010, at 08:55, Michael Van Canneyt wrote:
When I was debugging it (linux 64 bit) , the whole application
stopped on a floating point error somewhere in mozilla's Javascript
engine; I never got
around to debugging that.
Did you try
On 03 Jun 2010, at 10:24, Michael Van Canneyt wrote:
On Thu, 3 Jun 2010, Jonas Maebe wrote:
On 03 Jun 2010, at 08:55, Michael Van Canneyt wrote:
When I was debugging it (linux 64 bit) , the whole application
stopped on a floating point error somewhere in mozilla's
Javascript engine; I ne
On Thu, 3 Jun 2010, Jonas Maebe wrote:
On 03 Jun 2010, at 08:55, Michael Van Canneyt wrote:
When I was debugging it (linux 64 bit) , the whole application stopped on a
floating point error somewhere in mozilla's Javascript engine; I never got
around to debugging that.
Did you try disabli
On 03 Jun 2010, at 08:55, Michael Van Canneyt wrote:
When I was debugging it (linux 64 bit) , the whole application
stopped on a floating point error somewhere in mozilla's Javascript
engine; I never got
around to debugging that.
Did you try disabling floating point exceptions? A lot of C
Hi,
Are you cooperating with Phil on this ?
When I was debugging it (linux 64 bit) , the whole application stopped on a
floating point error somewhere in mozilla's Javascript engine; I never got
around to debugging that.
Have you seen this error too, or does the .GetServiceByContractID stop
13 matches
Mail list logo
