Optimised compile and "Dispose"

agraham · #1 (**permalink**) 03-11-2008, 01:11 PM

There is a behavioural difference between the IDE/legacy compile and optimised compile with "Dispose" on a library object. If you "New" an object from a library and "Dispose" it then in the IDE and legacy compiler the object seems to vanish and trying to reuse with another "New" errors. The optimised compiler however will happily renew it which could be useful in saving memory. Could the IDE/legacy compiler be brought into line with the optimising compiler in a future release?

Erel · #2 (**permalink**) 03-12-2008, 07:39 AM

The difference is that in the IDE you will need to add AddObject before the second "New".
There is no difference with the memory usage and the optimized compiler supports this AddObject as well.

The optimized compiler treats AddObject as a compiler directive. So calling it once (with AddObject or with Tools - Add Object) is enough.

agraham · #3 (**permalink**) 03-12-2008, 10:50 AM

Quote:

Originally Posted by Erel

The difference is that in the IDE you will need to add AddObject before the second "New".

Thanks Erel. Why didn't I think of that?

I must be getting too old for this lark