KisIterator, quantum and pixels

[Casper Boemann]

> > > > Mwah. I'm not convinced... (Don't take that too serious -- it's just
> > > > that I really, really hate premature optimization, especially if it
> > > > means complicating an interface. But I guess I'll just have to get
rid
> > > > of my Java prejudices.)
> > >
> > > Oh, what I don't understand is this -- isn't every iteration of an
> > > iterator a function call, too?
> >
> > Yes, in both cases you can make sure that all functions needed are
inline.
> > Then the compiler can do all sorts of optimizations - like moving
constant
> > stuff out of the loop.
>
> Which means, I take it, that there's not much reason to prefer one thing
or
> another?

I retract my earlier argument. I' don't feel safe though, but lets see.

> Currently we composite whole tiles at a time -- we simply pass a pointer
to
> their data. It might be better to rename the colour strategy's blit
methods
> to compose, and pass them iterators describing the section to be composed.
> Then we can get rid of all the tile cobbling in KisPainter.

Now you are talking - great idea

best regards
Casper Boemann