The below is an off-site archive of all tweets posted by @mjtsai ever

Recent tweets

@adamengst Hold down Option while choosing it from the menu.

via Tweetbot for iΟS in reply to adamengst

@boredzo Thanks for clarifying. That makes my life much easier, like it was a few hours ago. :-)

via Tweetbot for Mac in reply to boredzo

@boredzo If there were per-thread state, I could not use separate queues per document. But it's moot since you say documents are fine.

via Tweetbot for Mac in reply to boredzo

@boredzo I'm thinking of the NSXMLDocument case where I'm dispatching multiple blocks per document on the same serial queue.

via Tweetbot for Mac in reply to boredzo

@boredzo You can't ensure that they won't be interleaved on the same thread. But it's OK, I guess, since not called from a callback.

via Tweetbot for Mac in reply to boredzo

@boredzo In that case, it is easy to confine two objects to separate threads. But if you confine to separate serial queues…

via Tweetbot for Mac in reply to boredzo

@boredzo I was thinking of long-lived objects (e.g. documents) that you call methods on.

via Tweetbot for Mac in reply to boredzo

@boredzo 10.8 RN only mention a problem with reentrancy. Implies that separate parsers/documents are OK if called from same parent method.

via Tweetbot for Mac in reply to boredzo

@boredzo So the docs have been wrong all these years? Do I always have to use a child thread, to avoid colliding with Cocoa on main thread?

via Tweetbot for Mac in reply to boredzo

@boredzo BTW, that contradicts the docs: "…NSXMLParser is a thread-safe class as long as any given instance is only used in one thread."

via Tweetbot for Mac in reply to boredzo

@boredzo So all bets are off if you're using GCD and don't know the actual thread? Is NSXMLDocument safe?

via Tweetbot for Mac in reply to boredzo

@jasperblues I think you just put "dynamic" after "func".

via Tweetbot for Mac in reply to jasperblues

Doesn't seem to be anything wrong with my app's code signature. codesign just doesn't like VMware shared folders. Relieved but annoyed.

via Tweetbot for Mac

@jasperblues I agree with separate keywords, but I think “dynamic” should have been the default. Feels like having to type “nonfinal.”

via Hibari in reply to jasperblues

@jasperblues That part I think they got right in b5. The concerns are now separated, and there’s no implied deprecation for “dynamic.”

via Hibari in reply to jasperblues

@jasperblues So you have to mark each method “dynamic” individually: mjtsai.com/blog/2014/08/1…

via Hibari in reply to jasperblues

@jasperblues I think you have it backwards. As of b5, if you mark with “@objc” but not “dynamic” the compiler can inline the method.

via Hibari in reply to jasperblues

@kch @ccgus Because you don't want to leave the Mac running while you're out and about?

via Tweetbot for Mac in reply to kch

@ccgus @kch Do you mean a Linux/hosted server?

via Tweetbot for Mac in reply to ccgus

@nolobe_matt Getting SPF errors trying to reply to your e-mail. Tried multiple SMTP servers, so I think the issue's on your end.

via Tweetbot for Mac

@gte I'm having that problem, too, but alas it doesn't seem to be due to the cable.

via Tweetbot for Mac in reply to gte

@radiofreelunch @FogBugz Yes, Safari is still not officially supported with the performance upgrade.

via Tweetbot for Mac in reply to radiofreelunch