John Femiani wrote:
-----Original Message----- In my world, structs are tuples and tuples are structs. Duality. The minimum interface, if you guys do not want to fuss around with fusion, is this:
1) a metafunction to get the size of the tuple (dimensions for points). 2) a metafunction to get the element type given an index. 3) a get/at_c function that returns the actual data.
That's all. I can provide a non-intrusive adapter for that for Fusion easily for those who want to do more aggressive generic programming on these specialized tuples. Your interface itself need not have any hard dependency on fusion.
Regards, -- Joel de Guzman
Well coordinate access is only a part of what makes a point a hard-sell. There are hundreds of years of geometry and many API's to contend with as well. I kind of think (hope) that if the scope is kept extremely limited then it is possible to come up with generic point concepts, and maybe a reference implementation, that would make everybody happy. Is the boost wiki where these ideas could be fleshed out?
Sure. That's why I said "minimum". The minimum I need involves only structural information. I'm sure there are more domain specific interfaces required of points. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net