Re: Keeping a list of blocks

[Ivan Vučica]

Sounds good to me.

I'm not familiar with CFRunLoop APIs enough to say more. 

Is this just a list of blocks that will be run in the very next run loop step? If so, I see no other way except some kind of an array. Long term optimization might be a fixed-size C array allocated per-runloop that overflows into a CFArray if required, but CFArray should probably be smart enough to be fast enough even without doing such tricks.

On Wed, Apr 16, 2014 at 3:27 PM, Luboš Doležel <address@hidden> wrote:

Hi,

I'm currently implementing CFRunLoop. For the CFRunLoopPerformBlock() function, I need to keep a list of blocks to be performed next time the runloop loops.

What is the right way to keep a list of blocks?
My best idea was to fill in struct CFArrayCallBacks with callbacks that invoke _Block_copy/_Block_release.

Thanks!
--
Luboš Doležel


_______________________________________________
Gnustep-dev mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/gnustep-dev

--

Ivan Vučica

address@hidden