3 ms·
The article is comparing intrusive (see linux's list_head as an example) vs non-intrusive (std::list) lists. Given that comparison, intrusive lists (which the
by codys 12y ago
The article is comparing intrusive (see linux's list_head as an example) vs non-intrusive (std::list) lists.
Given that comparison, intrusive lists (which the article appears to argue for over std::list) are almost certainly better (barring some type of list node allocator that can somehow obtain locality with other nearby list nodes).
Once you throw std::vector (or similar dynamic arrays) in, it is a bit different (different trade offs), but that is not what this article is comparing
- sillysaurus3 12y agoYou're absolutely right. My apologies. I was only trying to say that in the context of gamedev, when choosing between list vs vector, list is almost always the worse option due to caching. But after re-reading, that's completely unrelated, as you say. Worse, ZeroMQ was going to be using list structures either way, so my point about ZeroMQ was both mistaken and irrelevant. I guess I should take a break for awhile.