I have been promoting the idea of people contributing any new functionality of GIL that they find useful by creating a GIL extension that is not originally in boost. This allows for an opportunity for people to try their code, flesh out some bugs, suggest changes to the design, etc. We can also use this as a mechanism to see how popular certain functionality is and use that to decide which functionality will make it into boost. That way, by the time it is proposed for inclusion into boost, the code will be more solid. This is how the new i/o extension by Christian originated. You can google for "gil extensions" to see a list of extensions (about a dozen or so) Lubomir On 7/22/10 10:54 AM, "Christian Henning" <chhenning@gmail.com> wrote:

Hi there,

...

64 bits pixels are interesting for accumulation buffers or internal computations. I think it could be a good thing to add these typedefs in gil. Is there any reason not to do it?

I don't know why it wasn't added to gil from the beginning. I'm not one of the original authors. I'm reluctant to add support for it since it would mean to make sure all functionality in gil is working correctly. Meaning creating a much more extensive unit test suite.

One of the great strengths of gil is the ability to create new pixel types by the user. Though just go ahead. ;-)

Regards, Christian _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost