Re: circular references

Marcus Börger wrote:

Putting out the warning is better. Eventually a damn note that the user shoot his self in the knee. But that would slow down performance.

I know, but memory leaks are pain in back. There is also another solution - it is possible to call destructor just before cleaning memory without taking care about reference numbers. They just shouldn't be unregistered from resources table before there are still references in userland.

AND a side note: even java does not handle that.

hmm... http://java.sun.com/docs/books/performance/1st_edition/html/JPAppGC.fm.html it seems they do ... regards Wojtek