Thanks. H&K is correct, that was just an example, what happens is there is a manage() method where the list is looped and depending on certain conditions remove() may be called. Normally I use clear if I want to clear the whole list.
Budman: Yeah pooling is the way to go for particles but I wanted to write an OOP version using lists first. Pooling is more old-school (sort of like I used to code on the Amiga) but faster of course - I may well do it as an alternative option in my framework. Also I want several lists at the moment so they can be drawn in a certain order (layers), with one big pooled list I couldn't do this, I'd have to make several pooled arrays which gets messy if they are declared globally as the handling routines can't be generic, or maybe they can...hmm.
Budman: Yeah pooling is the way to go for particles but I wanted to write an OOP version using lists first. Pooling is more old-school (sort of like I used to code on the Amiga) but faster of course - I may well do it as an alternative option in my framework. Also I want several lists at the moment so they can be drawn in a certain order (layers), with one big pooled list I couldn't do this, I'd have to make several pooled arrays which gets messy if they are declared globally as the handling routines can't be generic, or maybe they can...hmm.