Subject: Re: [boost] [GIL] Pixel Layout Padding?
From: TONGARI J (tongari95_at_[hidden])
Date: 2013-12-28 23:53:51
2013/12/29 Christian Henning <chhenning_at_[hidden]>
> > 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
> > overload 'at_c' to work with GIL, since those color_base_algorithm can
> > 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:
then the user would specialize boost::fusion::extension::at_impl for their
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk