>>You can also put DEBUGOUT THIS.CLASS in any method code. That way, you do not have to remember to remove it before distributing your app. It is harmless under runtime [as is ASSERT].
>
>I am not so sure about ASSERT; I sometimes got ugly errors when an assertion failed. It made the application crash, if I remember correctly.
>
>Probably the crash was due to a combination with some other problematic situation, but I don't remember all the details now.
>
>I understand the idea: that ASSERT won't produce any output for the end-user.

I have never had a problem with ASSERT in an app under runtime. I even tested it with SET ASSERTS ON issued at the start of the app followed by an ASSERT .F. and still got no failure message under runtime.