So, for the user, everything is well.
For the programmer, because he can use a top level try/catch/finally statement, if he is interested in knowing of the fact, this behaviour is a good compromise.
If you write code in FormCalc the behaviour is the exact opposite.
Syntax errors show up to the user. This may be admissible because, with thorough testing, it will happen in development-time.
But runtime errors always show up to the user. A big dialog, as tall as your code, shows the code to the user, and, at the bottom, possibly already off the screen, the description of runtime error. This may be an ugly description, depending on what failed.
As far as I know, there is no construct in the Form Calc language that allows catching errors, so you're stuck.
All this, imho, is an absurd, and can only be understood as some market-like feature.
Is there ANY undocumented way or dirty trick to prevent FormCalc error messages from displaying to the user?
Is there ANY undocumented way or dirty trick to catch FormCalc error messages, in FormCalc code?