Add to AttributeBinder:

std::vector bases;

New macro:

#define BIND_BASE(c) \
binding.bases.push_back(&c::binding);

Example to extend Foo in the original post:

class Baz : public Foo
{
public:

BIND_START;
BIND_BASE(Foo);
BIND(Baz, bool1, bool);
BIND(Baz, int2, int);
BIND(Baz, float3, float);
BIND_END;

Baz() : bool1(true), int2(2), float3(3) { }

bool bool1;
int int2;
float float3;
};

http://meshula.net/wordpress/?p=174

There are several reasons that many programmers consider type_info evil for games. I suppose the most glaring one is that it is incompletely implemented or non-existant on consoles. The second most glaring reason would be the reason multiple inheritance is considered bad; resolution can involve searching a vtable and doing matching. I wanted to stay away from roll your own RTTI because I wanted to keep this example really simple; but roll your own RTTI is actually pretty simple, so I should probably just go ahead and do it. I single stepped through the RTTI comparison code and discovered that MSVC generates code that strolls through the vtable, and ultimately does a strcmp against the type names it discovers (I didn’t dig deep enough to discover if the type name is baked into the code, or if it is constructed dynamically, which would be trebly 3vil). Vtable strolls and strcmps in game code freak me out, so I’m sold on not using built-in RTTI.

I’m still thinking of some light way to do polymorphic reflection. I’ll post again when I have something I like.

Suggestions are welcome!