Hi everyone,<br><br>I&#39;m currently setting up an image processing pipeline for large (out of core) GIS images using GIL.<br><br>I&#39;m quite glad with the results I get right now, but I stumbled upon a problem with the default image_view size / iterator handling.<br>
<br>Currently, image_view::size_type is defined as std::size_t, and image_view::end is implemented as begin()+(difference_type)<a class="code" href="http://stlab.adobe.com/gil/html/structboost_1_1gil_1_1size.html">size</a>();<br>
<br>As my images pixel count exceed the max value of std::size_t on my dev platform (win32), the image_view::end member function fails to give a valid iterator...<br><br>As nearly every types defined in image_view are given by the templated locator type, I&#39;m thinking that the size_type should not be an exception, and should be given by the locator type.<br>
<br>I also tend to think that the &#39;image iterators&#39; should not share the difference_type type with the &#39;1D iterators&#39; - but these are mainly performance considerations in my case, as my image iterators should be 64bits, and my 1d iterators can be 32 bits.<br>
<br>For now, I changed my GIL working copy to patch image_view definition, as I did not see any way to work around the iterator problem. Did I miss anything ? Is there any user-level workaround I could use, or should the image_view class be modified ?<br>
<br>Any thoughts would be welcome :)<br>Thanks,<br><br>Nicolas.<br><br>