Wrong.
The problem is, theoretially the list should be cleared when it is "removed", thats what the delete method declares.
Stupidly this one isn't called quite often (never?) which is most likely because BRL implemented the linked list as a double linked list in which the "core" link is always the same (first is corelink.next and last is corelink.prev and the corelink is double linked to both so the list "never ends). You can cycle endless in both directions, forward / backward without ever reaching an end.
Due to that structure, if clear is not executed, the whole list (beside the TList reference that referenced to _head) will remain in RAM but you won't be able to get your hands on it anymore.
As mentioned, clear is part of the delete method and should be called ... it should and thats the problem ...
The problem is, theoretially the list should be cleared when it is "removed", thats what the delete method declares.
Stupidly this one isn't called quite often (never?) which is most likely because BRL implemented the linked list as a double linked list in which the "core" link is always the same (first is corelink.next and last is corelink.prev and the corelink is double linked to both so the list "never ends). You can cycle endless in both directions, forward / backward without ever reaching an end.
Due to that structure, if clear is not executed, the whole list (beside the TList reference that referenced to _head) will remain in RAM but you won't be able to get your hands on it anymore.
As mentioned, clear is part of the delete method and should be called ... it should and thats the problem ...