Hi folks,
The thing is, it might be the case that we only have one loops thing in
the pipelines we have in OpenJDK, but thanks to Cacio (hohum) we must
consider that there are other implementations out there... which might
want to take completely different approaches. So better to keep it clean
and nice and not make any assumptions. Right?
/ Roman
Mario Torre wrote:
Il giorno gio, 18/06/2009 alle 16.01 -0400, Roman Kennke ha scritto:
Hi Jim,
If only one instance of the loops is used during the lifetime of a
Surface, then we can easily keep this instance there instead of the
SG2D, validating would not initialize any new objects, but only put
stuff together that is already present in the SurfaceData anyway. Or did
I get something wrong here?
i
This make sense, because we can initialise the loops in one place and
live with them. If things will change, there will be no risk to forget
because the whole thing is in one single place now and has no extra
dependencies anymore, but from what I see the loops are always the same
from a practical point of view (but I'll check this a bit better just in
case).
I like both this and the first approach proposed by Jim, so is up to you
to decide what to do :)
Cheers,
Mario
