Dipping my toe back into C#, I see I've become a bit rusty.

I have defined a List<> of objects I've defined. Every so often, I need to check for -- and remove -- any items in the list that meet a certain "death" condition. What I'm doing is using a for-loop to update all the objects, and then as they are updated, a certain value changes... If that value reaches 0, that item needs to be removed from the list on the next "death" check.

I can't use foreach, as the iterator will be nullified as I go along removing things while it's running. I can't remove the item during the for-loop update, as it will mess with the indexing... so, I'm kind of at a loss as to how to achieve my goal. I really don't know what I *can* do to get rid of these "dead" objects.

So, what should I be doing?

_________________
What most people don't understand about "enlightenment" is that it is not an end-goal; but where you find yourself just before taking a new "first step."

Make your own loop logic, rather than using a For-loop

_________________
I ain't pushing no moon buttons.

Mark them as dead. When a new object gets created, place it in a dead object's slot.

Alternatively, in a for loop, you'll have to decrement your counter before you continue, otherwise you'll skip elements. The better way to do that is to iterate backwards. http://stackoverflow.com/questions/308466/how-to-modify-or-delete-items-from-an-enumerable-collection-while-iterating-throu



People are saying the best way to do it is by using delegates, something I've never dabbled with. Apparently something along the lines of

_________________
Whatever the mind can conceive and believe, it can achieve

I did a similar thing with my particle emitters. When an emitter expires, some particles it has spawned may still exist, and we need keep hold of the emitter so that it's physics parameters can continue to be applied to those particles. So we need to wait for those particles to die before we can kill the emitter.

_________________
I ain't pushing no moon buttons.

Thank you, you two. I'll get to work on it.


I'm not really sure I understand what you're getting at, Jasmine; could you elaborate on this?

_________________
What most people don't understand about "enlightenment" is that it is not an end-goal; but where you find yourself just before taking a new "first step."

I just had a dig around the remove() methods. I'm sure I was doing something like this last year and the remove method returned an iterator pointing at the node immediately before (or after, can't remember which) the deleted one (or the new head/tail if there was no previous/next available).

However, that docs make no mention of it.

_________________
10 PRINT "Bad Monkey ";
20 GOTO 10

_________________
I ain't pushing no moon buttons.