> Most programming environments have a way to deal with runtime errors. Many > good ones have constructs like try/catch/throw. 4D really needs something > like this.
I second this too, it would be much better than the present state. But regarding the discussion about runtime errors, pl4ease read this short article about Java's RunTimeException (a more or less official statement in the docs of Java): <https://docs.oracle.com/javase/tutorial/essential/exceptions/runtime.html> I quote from there: > Here's the bottom line guideline: If a client can reasonably be expected to > recover > from an exception, make it a checked exception. If a client cannot do > anything to > recover from the exception, make it an unchecked exception. Regards Lutz -- Lutz Epperlein ---------------------------------------------- Agendo Gesellschaft für politische Planung mbH Köpenicker Str. 9 10997 Berlin http://www.agendo.de/ ---------------------------------------------- ********************************************************************** 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 **********************************************************************
