Re: Compile time container, run-time execution.
On Feb 4, 2:25 pm, Victor Bazarov <v.Abaza...@comAcast.net> wrote:
puzzlecracker wrote:
On Feb 4, 1:12 pm, Victor Bazarov <v.Abaza...@comAcast.net> wrote:
puzzlecracker wrote:
template<class Derived>
struct auto_register
{
//singleton that hold existing Derived
static list<Derived*>& container()
{static list<Derived*> obj_list;return obj_list;}
auto_register()
{
container().push_back(static_cast<Derived*>(this));
}
~auto_register()
{
container().erase(static_cast<Derived*>(this));
}
};
And then:
class Foo:auto_register<Foo>
{
};
I think that will work. The other thing OP will have to implement =
is
a destructo that will remove/unregister objects.
You mean like the one in 'auto_register' (called ~auto_register)?
V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask
yeah just like that... but my question is whether the solution is
workable as I see it.
As you "see it"? How do *you* see it?
V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask
stop being a dick!