Subject: Re: [boost] GIL io_new review
From: Phil Endecott (spam_from_boost_dev_at_[hidden])
Date: 2010-12-11 18:29:29
Domagoj Saric wrote:
> "Phil Endecott" <spam_from_boost_dev_at_[hidden]> wrote in message
> Well I must still say I do not understand why must you read entire rows of
> input tiles (1400*5000 in length)
Because I can, and it gives me fast and simple code.
> why can't you just read individual 5k
> input tiles and chop each of those into the smaller output PNGs and then
> move on...yes the 5000%256!=0 issue might require reading up to 4 input
> tiles and/or remembering some of the edge data for the cross-border input
> tiles and/or maybe of the input tile which in turn would require a (much)
> more complex code...but I do not really see the issue with that
I prefer fast and simple code to either fast-and-complex or slow-and-simple.
>> So I just want the library to provide the simple
>> open/read-row/write-row/close functionality for the image files, and to
>> supply types that I can use for pixel_t, etc.
> Independent of the rest of the discussion/issues, yes I would agree that
> explicit read/write row would be a valuable part of the interface...
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk