In part 1 I discussed bridging a Swift reference through a C void pointer. This was for the purpose of wrapping C libraries but maintaining an object oriented approach that ties the callback to a specific instance. However if you are not fortunate enough to have a C API that offers a void pointer to pass a context, then this approach will work as long as the callback function is called synchronously. That is to say the callback function is invoked before the C function returns and on the same thread as the call to the C function. While this is less common it can crop up from time to time. I found an occurrence of this when I wanted a B-Tree implementation and tried calling the DBM module of BSD.
Since the callback will be made synchronously on the calling thread. We can make use of a capability of dispatch queues, that lets us set a specific key/value pair on a dispatch queue and fetch it within the callback function. The name specific is likely taken from pthreads for thread specific data. To do this you need to create an instance of DispatchSpecificKey and then set the context you wish to pass to the callback function prior to calling the C function.
Subscribe to:
Post Comments (Atom)
-
Core Data abstracts a lot of the low level details of storage away for programmers, and that’s a good thing however sometimes it’s useful t...
-
With iOS 13 Apple added some convenience methods to NSData to compress and decompress data using a set of compression algorithms. Zlib is re...
-
Overview When working on software projects, fixing bugs is an inevitable fact of life. Sometimes you're lucky and the nature of the is...
This comment has been removed by the author.
ReplyDeleteSitus Judi Slot Online Gacor 2021 - JT Hub
ReplyDeleteSitus Judi Slot Online Gacor 서산 출장안마 2021 Terpercaya 경산 출장샵 2021. Daftar 화성 출장안마 & Mainkan slot gacor 김해 출장샵 slot online, casino online sekarang dan bonus 충청남도 출장안마 melimpah!