Michael Bien wrote

The variable is package private. Would it be OK for you to write a
utility and place it in com.jogamp.opencl to access the buffer?
buffer = Hack.get(events);

Or maybe you have a better idea how to solve that..

Michael Bien wrote

> Incidentally clAmdFft uses size_t * in a few places, can I safely just
> assume that size_t is related to the platform pointer size?  I was going to
> create my own SizeTBuffer type or some-such to make sure, but JOCL just uses
> a PointerBuffer, and appears none the worse for it.
I am using NativeSizeBuffer* in my repository for size_t to separate
both types (and other reasons). However if you want to stay compatible
with jogamp you probably better stick with PB.