Fabio,

Get real please. Doing nothing and consuming 0 CPU cycles is not the same thing. Doing nothing means that it will not raise the dialog that it does in the dev environment.

As I said in the other post, If you don't want the asserts to consume any CPU cycles in runtime wrap them with a #ifdef to keep them out of your exe.

It's really not worth the effort IMHO because asserts should not be used inside loops where you'd notice the miniscule performance hit.

>The assert command simply does nothing in the runtime, so there's no need to have the code removed.
>...
>
>
>David, for does nothing, VFP it cannot demand of the time.
>
>BUT THIS IS NOT TRUE, at runtime VFP evaluate ASSERT token, it not eval the expression
>
>ASSERT is fast, but it consumes a little time.