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?
Uncategorized
3
Posts
2
Posters
0
Views
-
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?
-
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 self-registering inventory?
-
@azonenberg self-registering inventory?
@gsuberland That seems as reasonable a term as any for my implementation, but doesn't seem to be a pre-existing term of art
-
R relay@relay.infosec.exchange shared this topic
