View Single Post
I'm not familiar with that code, and I would agree that that causes one to do a bit of a double-take when looking at the code, but offhand it looks intentional. If you look around to see where listSize gets changed, it's in three places, and all three have the same pattern of assignment directly inline with calculation for memory allocation.