Get short, timely messages from Matt Gallagher.

Twitter is a rich source of instantly updated information. It's easy to stay updated on an incredibly wide variety of topics. Join today and follow @cocoawithlove.

Get updates via SMS by texting follow cocoawithlove to 40404 in the United States
Codes for other countries

Two-way (sending and receiving) short codes:
Country Code For customers of
Australia
  • 0198089488 Telstra
Canada
  • 21212 (any)
United Kingdom
  • 86444 Vodafone, Orange, 3, O2
Indonesia
  • 89887 AXIS, 3, Telkomsel
Ireland
  • 51210 O2
India
  • 53000 Bharti Airtel, Videocon
Jordan
  • 90903 Zain
New Zealand
  • 8987 Vodafone, Telecom NZ
United States
  • 40404 (any)

cocoawithlove

  1. @basilshkara I'll rename now but complain later. Apple's private names now too generic. I can't use setFileName: on own objects anymore? ಠ_ಠ
  2. @basilshkara Time to demand that Apple prefix all their "non-public APIs". We can't avoid generically named methods that we don't know about
  3. @markaufflick Yes it seems to be a mistake in Apple's non-public API detection. A change since 22 Oct when same code approved without issue.
  4. @markaufflick Declared but not defined CoreData attributes and 1-to-1 properties. Never an issue before. Suddenly AppStore flagged them all.
  5. @rentzsch No this isn't a clash with an actual method name it's unique properties I've had in my code for over a year like setTextDirection:
  6. AppStore rejected my Core Data dynamic property accessor methods as "non-public APIs". Anyone else seeing this issue in the last week or so?
  7. @JoergBastian I haven't been on Twitter in 3 weeks. I hope you found the solution to your ServeToMe 3.6.5 problem (re-download for bug fix).
  8. @gruber Regarding bit.ly/tehwrH there is 1 reason to publish future concept videos: they're prior art against future obvious patents.
  9. @bignoggins I expect non-ARC will be practically gone in 12 months (ARC is that good) but I can't really discuss until Xcode 4.2 is released
  10. Oh, dammit! I make my first tweet in weeks and when I get a reply I innocently click on the link. I lose the Twitter spam avoidance game :-(
  11. @ivucica Thanks, I've fixed the post. I added syntax highlighting to my blog's code and it's required that I clean out old markup like this.
  12. @sirslinky @tom__ We have a FAQ article on the StreamToMe 3.6.2 crash bug here: bit.ly/qAj0kH including some workaround instructions.
  13. Reading http://bit.ly/oMABCd by @brentsimmons I really wish that synthesize was implied for properties unless "dynamic" was explicitly used.
  14. @eridius Yes a protocol would help disambiguate since casting Class<SomeProtocol> or id<SomeProtocol> adds usable type info for the compiler
  15. Today's post I look at a weakness in Objective-C's weak typing that causes method parameters to get turned into garbage http://bit.ly/kn7hbL
  16. Open sourcing my oldest iOS application in this week's blog post. Rewritten since original code from 2008 was scary bad http://bit.ly/ixoGmt
  17. Being a developer sucks all the fun out of a WWDC keynote. New iOS5 betas and Lion betas at once means I have so much work to do in my apps.
  18. Yeah I'm not in official LANoire creds. Not surprised: for me MotionScan was 5 yrs ago. Shocked lanoirecredits.com found me @chrismiles @orj
  19. Here are some reusable NSURLConnection delegate classes for fetching data, XML and JSON via HTTP that I use in projects http://bit.ly/j09NLo
  20. A quick Mac app: using Core Image on the Mac to make dialog sheets stand out from the window to which they're attached. http://bit.ly/iAAS3Q