Er, what's the point of having a forceful delete?! All references pointing to it won't be equal to null anyway. The garbage collector is one of the best things about Max, and using manual delete makes it pointless
Yes they will. I'm not talking about replacing it completely, I'm talking about offering the option.
The refs system will be left in place, but in controlled siturations you can circumvent it and use your own direct.(It seems possible from the code, it's all there, including ref inc'ing and dinking.)
I feel it's needed because nearly everything I've done so far(Bar trinity, but that's only thanks to a custom profiler build from scratch) has exhibited massive memory leaks in tight siturations.
Like an Ase loader balooning to 900mb, despite numerous methods of flushing the memory.(Once per loop, over every 10,000 loops. At the end of every scope, within custom modules..
But nothing really seems to stem the tide of leaked memory in *Certain*(Not all) siturations.
I think a lot of is this is to do with HOW it actually works internally, as it seems to fragment memory a helluva lot in complex tasks.
It would be great, if it worked however, or the docs were updated to the point of clarity.