On Jul 24, 2014, at 4:43 PM, Quincey Morris wrote:
> On Jul 24, 2014, at 11:58 , edward taffel wrote:
>
>> NSStreamEventOpenCompleted = 1 << 0,
>>
>> a point of style?
>
> Supposition:
>
> It’s point of API self-documentation. The shift indicates that this is a bit
> mask (or bit field) val
On Jul 24, 2014, at 11:58 , edward taffel wrote:
> NSStreamEventOpenCompleted = 1 << 0,
>
> a point of style?
Supposition:
It’s point of API self-documentation. The shift indicates that this is a bit
mask (or bit field) value, and hence that the enum’s members can usefully be
OR’ed together.
On Jul 24, 2014, at 2:46 PM, Ken Thomases wrote:
> On Jul 24, 2014, at 1:05 PM, Alex Zavatone wrote:
>
>> - (void)stream:(NSStream *)theStream handleEvent:(NSStreamEvent)
>> streamEvent,
>>
>> I'll log streamEvent and in the case of 4, which is is supposed to be
>> typdefed to NSStreamEvent
On Jul 24, 2014, at 2:45 PM, Sean McBride wrote:
> On Thu, 24 Jul 2014 14:05:17 -0400, Alex Zavatone said:
>
>> If I change
>>
>> case NSStreamEventEndEncountered:
>>
>> to
>>
>> case 4:
>>
>> the event is caught.
>>
>> Since NSStreamEventEndEncountered is supposed to = 1UL << 4 in t
On Jul 24, 2014, at 1:05 PM, Alex Zavatone wrote:
> - (void)stream:(NSStream *)theStream handleEvent:(NSStreamEvent) streamEvent,
>
> I'll log streamEvent and in the case of 4, which is is supposed to be
> typdefed to NSStreamEventEndEncountered, it's never trapped at all.
NSStreamEventEndEnc
On Thu, 24 Jul 2014 14:05:17 -0400, Alex Zavatone said:
>If I change
>
>case NSStreamEventEndEncountered:
>
>to
>
>case 4:
>
>the event is caught.
>
>Since NSStreamEventEndEncountered is supposed to = 1UL << 4 in the
>NSStream header, does anyone have any idea what's going on here?
Um,
