Re: [Algorithms] Complexity of new hardware

[Gregory J. <gj...@da...>]

> this provides the optimum implementation in the sense that it relies 
> only on static init (no dynamic memory allocations) and it doesn't 
> require member definition to be separate from declaration (it's all in 
> the .h file).

Agreed -- ours works the same way. Class and property reflection info is
stored as a static linked list, and the reflection info is declared in the
header (of course, in order for the static registration magic to work, you
do need a single HYP_CLASS_IMPL() macro in the .cpp file).
...

> It's still repeating yourself, though.

Our system has all of the benefits described, with no repetitions -- the
declaration of the property (member) reflection info *is* the declaration of
the struct/class field.

Greg