As some may remember I was going nuts trying to track down why when I 
loaded an interpreted version of a component 4D would error on startup 
with a stack overflow error.

Thanks to 4D tech support, the problem was discovered.

I had placed a Catch (Runtime explorer -> Catch) which referenced a 
component method's return value, apparently, 4D did not like that AT. 
ALL.

v15 gave a dialog - before any code could run with a stack overflow 
error.
v16 just crashed silently to the desktop.

so... don't do that  :)

Chip
We have done so much, with so little, for so long;
We are now qualified to anything with nothing <sigh>
  - unknown
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to