29 Dec
2013
29 Dec
'13
4:53 a.m.
2013/12/29 Christian Henning
For example, gil::at_c for each existed pixel is defined by overloading, that's a big problem for extension, the custom types after come cannot just overload 'at_c' to work with GIL, since those color_base_algorithm can only see those 'at_c' which are already defined before, not after. As the result, you see the huge "gil_concept.hpp" with lots of forward declaration :/
Can this be improved, like what Fusion does?
Would you provide some code to play around with?
May I introduce you to the mechanism Fusion used: https://github.com/boostorg/fusion/blob/master/include/boost/fusion/sequence... then the user would specialize boost::fusion::extension::at_impl for their own type. HTH