edit: wrong post. please dete it
Anyway, having an optimized count method of an extended TList, in some situations can improve the collection performance. Obviously there can be some compatibility issues. I will use an extended version of TList for a module I'm writting, as it is using a lot of count() calls for large TLists. These Tlists are being used internally by the module, and there's no speciffic TLink manipulation, so in this situation, I think it can be a good improvement of performance.
As soon as I have tested it properly, I can provide some results, if anyone here is interested.
Anyway, having an optimized count method of an extended TList, in some situations can improve the collection performance. Obviously there can be some compatibility issues. I will use an extended version of TList for a module I'm writting, as it is using a lot of count() calls for large TLists. These Tlists are being used internally by the module, and there's no speciffic TLink manipulation, so in this situation, I think it can be a good improvement of performance.
As soon as I have tested it properly, I can provide some results, if anyone here is interested.