> And as a hint, try not to use the destructor Destroy
> directly.
> The documentation suggests using Free because it
> checks whether the object for which you are calling
> Free is Nil or not. If it is Nil, it will not call
> Destroy.
>   
someobject.free still requires a valid someobject pointer with which to 
call free.

If you want the above behavior, you must call FreeAndNil(someobject).

Doug

Reply via email to