Quote:Original post by Mawr
Made a reference to the end of the list, and tested against that instead of calling dustlist.end(); every loop.

I'm not sure what your saying, you can't test an iterator with a reference, certainly if your not modifying the list you can cache a copy of the end iterator e.g.

for(std::list<dust>::const_iterator itr = dustlist.begin(),    end = dustlist.end();    itr != end;    ++itr) { /*...*/ }

but we mean't to use a reference type at the beginning of the loop.

Quote:Original post by Mawr
But I don't understand how making a reference to the iterator for my list would improve performance. I thought in this situation 'it' as already a reference?

list iterator will typically encapsulate a list node that refers to a node in the list, list iterator is a user-defined type with overloaded operators that mick schematics of a pointer, your really calling a member function so to avoid the overhead of the function call you cache a reference or constant reference (even better) and in all intents a reference is the object presto no more function calls.

By the way did you get a performance increase?

Guess my nomenclature is a bit bad. Here is the code I used to replace my old code.



I did get a signifigant boost to performance. While my program wasn't really that slow before on my machine, I wanted to know if there was any easy optimizations I could do, for the simple fact I'd know them.

I shifted the most time intensive calls from the ones I mentioned in my orignal post to void Draw(), void Update(), and float TransulatePoint(). And because some of my other functions were made in the same style, I improved them also with what you guys suggested.

Though I still have some questions, I think I understand moving away from it->member to const dust& d=*it, I'll try that next. But now zombie items inside the list? I thought the statement it=dustlist.erase(it); removed the item at position it, preventing any zombie items from being inside the list. Also, while watching the amount of memory my program uses, it stabilizes fairly quickly at a reasonable number (7 megabytes or so).