Thanks
On Wed, 18 Apr 2018 14:17:29 +0200, Arnaud de Montard via 4D_Tech wrote:
>
>> Le 16 avr. 2018 à 18:38, Chip Scheide via 4D_Tech
>> <4d_tech@lists.4d.com> a écrit :
>>
>> What kind of over head is there on setting and clearing On Err Call?
>>
>> If On Err Call is being set and cleared in
> Le 16 avr. 2018 à 18:38, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> a
> écrit :
>
> What kind of over head is there on setting and clearing On Err Call?
>
> If On Err Call is being set and cleared in a loop, is there a
> significant overhead issue?
I tested that 3 or 4 years ago: doesn
Thanks!
that was sort of my thinking, but... then I over thought, and figured maybe
there was some sort of overhead which would make this an issue.
> even if the time difference were significant (say, 0.0005 second per
> install/uninstall) I would not consider is an over head. in fact I
> wou
even if the time difference were significant (say, 0.0005 second per
install/uninstall) I would not consider is an over head. in fact I would
happily ignore it even if the delay was 1000 times worse (which I doubt),
because the risk of missing a bug by over extending the scope of ON ERR CALL
wo
Hi Chip, I would run some tests to find out what the impact is.
Capture the time, run the code a number of times (say 1000) and then capture
the time again. Do this with the On Err Call and without and you should get a
sense of the impact.
If your production environment runs compiled, then this
What kind of over head is there on setting and clearing On Err Call?
If On Err Call is being set and cleared in a loop, is there a
significant overhead issue?
ex:
For($i;1;Some_Integer_Value)
on err call("Error_Handler")
do stuff which could generate error
on err call ("")
do other stuf
6 matches
Mail list logo
