What is wrong with making this optional? Think of loop based repetitive code demanding the highest level of performance ( for example real-time or DSP related code ) - in that situation one would not want any error checks inside the loop in the final release.
Of course the same program might very well use lots of asserts left in place in the final release elsewhere where performance is not an issue, but the decision ought to be left to the developer. On 22/11/06 15:12, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > You could write your Assert to do nothing in a release build, but it's > not clear to me why you would want to. At the very least, it should > log the error to a file that you can then ask your users for when > things seem to go wrong. (And things WILL go wrong.) _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
