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

Country	Code	For customers of
United States	40404	(any)
Canada	21212	(any)
United Kingdom	86444	Vodafone, Orange, 3, O2
Brazil	40404	Nextel, TIM
Haiti	40404	Digicel, Voila
Ireland	51210	Vodafone, O2
India	53000	Bharti Airtel, Videocon, Reliance
Indonesia	89887	AXIS, 3, Telkomsel, Indosat, XL Axiata
Italy	4880804	Wind
3424486444	Vodafone
» See SMS short codes for other countries

Petrifying Horror ‏@boredzo 22 Aug 2014

PSA: Don't start a second NSXMLParser on the same thread where another NSXMLParser is already running, or you will have a bad time.
3 retweets 5 likes
Michael Tsai ‏@mjtsai 22 Aug 2014

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

@mjtsai You can use a serial queue, but not concurrent, for that reason. NSXMLDoc/Element: Probably the same story; haven't looked deeply.
Michael Tsai ‏@mjtsai 22 Aug 2014

@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?
Petrifying Horror ‏@boredzo 22 Aug 2014

@mjtsai The docs aren't wrong as such, just incomplete. (The other half is buried in the 10.8 RN.)

‏@mjtsai

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

7:09 PM - 22 Aug 2014

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.