Re: Complexity of new hardware

> 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


------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
GDAlgorithms-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gdalgorithms-list
Archives:
http://sourceforge.net/mailarchive/forum.php?forum_name=gdalgorithms-list