> On Oct 7, 2016, at 10:05 AM, Quincey Morris
> wrote:
>
> Surely “anyone reading the code” is going to recognize “dispatch_semaphore”
> as something to do with a semaphore, including people from other platforms?
You’re right; I was [mis]remembering a classic semaphore as being a simple
mute
> On Oct 7, 2016, at 6:51 PM, Quincey Morris
> wrote:
>
> Looking at the documentation a bit more carefully, though, I think it’s
> implicit. Each thread, it says, can have a “current” NSProgress object, but
> there can be parent-child relationships between NSProgress objects across
> thread
> On Oct 7, 2016, at 5:03 PM, Gabriel Zachmann wrote:
>
> One thing that surprised me a little, in light of the fact that aliases are
> completely different from symlinks,
> is that
> [url getResourceValue: &isAlias forKey: NSURLIsAliasFileKey error: nil]
> yields true for both aliases and s
> On Oct 7, 2016, at 2:25 PM, a...@hiddenreflex.com wrote:
>
> For some mysterious reason our SPDY encrypted proxy fails in our chromium
> based browser only in Mac OS X Sierra. It works fine in every other
> operating system. We're getting a "CERTIFICATE_INVALID_ERROR" even though
> our certifi
On Oct 8, 2016, at 00:42 , J.E. Schotsman wrote:
>
> So it’s still true that the root NSProgress object must update its KVO
> compliant properties on the main thread for bindings to work, I suppose.
Well, looking back at the code I actually wrote, I didn’t use this assumption,
so now I’m not s
> On 08 Oct 2016, at 03:51,Quincey Morris wrote:
>
> Looking at the documentation a bit more carefully, though, I think it’s
> implicit. Each thread, it says, can have a “current” NSProgress object, but
> there can be parent-child relationships between NSProgress objects across
> thread bounda
