Hey! On Thu, May 7, 2015 at 2:47 AM, Lenahan, Charlie <charlie.lenahan at intel.com> wrote: > I have a similar change that was for our objective-c/darwin/ios branch. > > I didn?t use a full structure thought(just a callbackParam), because > the app is responsible for unregisterResource and know when to delete its > context.
OK, I figured that OCCreateResource has a companion (or several) that perform the opposite. That's taken care of in my bindings. > If it?s blocking you I can try pushing that change. The absence of the context is not blocking me, but only because I resorted to using a C implementation of function closures (libffi) to generate a function at runtime that receives the context as an extra parameter. I consider this to be an exotic and risky solution and one that a proper underlying API should make unnecessary. Thus, I would very much welcome your change! TIA for your help, Gabriel
