> Le 5 févr. 2017 à 05:46, Keisuke Miyako <keisuke.miy...@4d.com> a écrit : > > I am not sure if an out of range is something you would want trap and catch > with ON ERR CALL, > there is nothing you could do to recover from it. > > ON ERR CALL, in my opinion, > is only meaningful in the context of an unreliable player (the user, network, > or file system) > otherwise, for things like type mismatch, missing parameters, or out of range, > you only have yourself to blame and an ASSERT seems more appropriate if the > route to that line of code is considerably complex.
Agree. I was just surprised by the difference without/with catch error: without throws successively 2 errors, while with the whole line seems to be executed before 4d "reacts". -- Arnaud de Montard ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
