Tim, As we all know this sort of thing isn't what I'm particularly good at - but maybe it's the case that the compiler hits the -20007 error before getting to the more specific characterization that it's caused by incompatible types. If it's not that then I agree it would be nice if the messages were the same.
I wan't aware that the error handler would get tripped by that though. That may be the buried lede here - and an argument for installing error handlers. Makes it easier to run interpreted and mimic compiled. Wouldn't it be cool if we could toggle the interpreted mode to run in strict typing mode to mimic compiled? On Tue, Oct 31, 2017 at 4:08 PM, Tim Nevels via 4D_Tech < [email protected]> wrote: > ... > They are supposed to make interpreted code produce the same kind of error > messages that occur in compiled code. This is an example of that not being > done. Obviously the guys doing the compiler work don’t talk to the guys > that are doing the interpreter work. -- Kirk Brooks San Francisco, CA ======================= *The only thing necessary for the triumph of evil is for good men to do nothing.* *- Edmund Burke* ********************************************************************** 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:[email protected] **********************************************************************
