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 > 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 would be too expensive. I would totally dismiss > the question of whether ON ERR CALL creates an overhead an always use > it immediately before and after the command whose exception I want to > catch. > > 2018/04/18 5:50、Dani Beaubien via 4D_Tech > <[email protected]<mailto:[email protected]>> のメール： > > 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. > > > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ------------ Hell is other people Jean-Paul Sartre ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
