if you think you can optimize something just fork the repository on
github and do your work.
we can take a look at it later and integrate it if it makes sense (e.g.
does not overcomplicate things + does not break something).
contributions are always welcome.
but a single iterator per frame is usually not the problem.
On 06/22/2010 12:11 AM, Taif [via jogamp] wrote:
I've recently fallen love with the java allocation
a single FPS counter which displays the FPS String would cause more
garbage as an iterator. But in both cases you won't notice it. The
objects would die young and wouldn't be evacuated in the young gc phase
- which is very fast compared to old generation sweeps.
But again if you have a cool idea how to get rid of it... you know
where the repo is :). API Bindings should be GC neutral i fully agree.
On 06/24/2010 04:00 PM, jeff [via jogamp] wrote:
Taif might be right. anything that is allocated will be
GCed once in a while. even if the GC happens rarely, it will happen
evenutally and on slow machines this causes a framelag.