>>
>>>We use a little function called Developer( tcMessage, tlLog ) that tests if wwe are at runtime or not.
>>>
>>>If we're in development environment, it shows the message, giving the options to suspend, cancel, debug or ignore.
>>>
>>>If we're in production it just passes by, logging the message to a file if the second parameter is True.
>>>
>>>It is that kind of stupid functions that you just can't live without.
>>
>>I know, I know. You can use ASSERT for this, but we started doing this in FPD 2.6, and ASSERT don't allow you to log the message. 8-)
>
>At this point I need to say that too much unneccsary code slow things down. I make it a habbit of removing dubugging information before compiling a final release.

As usual, we don't use this inside of a thight loop, but even then, we periodically clean up the code ffor such things. There are times that just get annoying seeing other developer self-annotation. 8-)

Indeed, we have an entry in our development menu (with it's proper shortcut), that basically pastes in the code something like:

* MS, 22/01/2001
Developer( "MS" )

So we can review the calls later. Our internal norm is: "If you didn't specified another expiration term, all developers can be wiped after a week."

The results is many times, obviously, just like:

* MS, 22/01/2001: The one that deletes this call would suffer the 
* 7 plagues od Egypt and a kick in the ass!!!
Developer( "MS. Why that sh*t isn't working???" )

You know... Teamwork! 8-)