Is there a name for a design paradigm where a class has a static "list of all objects of my own type" member, inserted by the constructor and removed by the destructor, and you can iterate over them for $REASONS?
@azonenberg If it's C++ then a member can't be both static and set up by the constructor of the class it's in. I'm sure you know this but I'm just being pedantic.
We use that pattern a lot though, sometimes just to contain a fixed list of constants, sometimes a collection of pointers to members that have to be visited in some way. So I'd like to know the name for it too.