Posted by Christof (193.170.190.x) on October 16 2019, 2:52pm:
Awesome, thanks! Great to see it's part of WDL, so I don't have to use Boost :-)
Posted by Justin on October 16 2019, 3:42pm:
Sorry it's so poorly documented...
Posted by Christof (193.170.190.x) on October 16 2019, 5:05pm:
No worries! Now that I had a look a the sources, the non-Windows version of the shared memory interface uses sockets instead of actual shared memory (via shm_open), is there a specific reason for this?
Posted by Justin on October 16 2019, 5:08pm:
Ah yeah, because you ended up having to use a socket in order to synchronize (the equivalent of a named event which is used on Windows), so might as well shove the data through there anyway, which works well.
Posted by Justin on October 16 2019, 7:45pm:
Heh if you want to convert it and see if shm/semaphore is faster, be my guest ;) What about on macOS?
Posted by Christof (193.170.190.x) on October 16 2019, 8:41pm:
Ha! Looks like OSX doesn't support unnamed semaphores, but apparantly you can achieve the same thing with GCD's dispatch_semaphore_t. Anyway, I'll try to implement it and benchmark against the socket implementation (but not before December). Actually, I thought 32-bit plugins are mainly a Windows thing, but then I got some feature requests from macOS users who still use 32-bit plugins (and they won't upgrade to Catalina :-D)