ObjectiveCFacts's profile picture. when to use retainCount? always

Objective-C

@ObjectiveCFacts

when to use retainCount? always

parameter names arent necessary, but you should because then maybe daddy will hug me


modern objective-c syntax include nsmaptable literal: @{^key^ : ^value^};


prevent race conditions by wrapping app in @synthesized. atomic propertie help too


@LxndrKvcs no, it like saying “don’t put toilet in every room”


our guide to kvo: don’t


the best thing about 64 bits? you are right: the 32 extra bits


for a #fun night out on the town go to any bar and ask for the objective c special to get kicked out immediately


kvo — just say no (kvno!)


the only data structure in flat objective c is array, no trees allowed (too skeuomorphic)


introducing objective c 3.0, now with a flatter design


nsmaptable? more like nsfaptable


objective c is the german of programming languages


mark delegates as strong references to ensure they’re always around


key-value coding was originally called key-value trolling


macros are a great way to promote code reuse


use random number generator in your unit test to achieve good code coverage


namespaces are just poor mans class prefixes


dependency problems? just copy paste


you know what objective c really need? generics! lol


a memory warning occurs whenever any object's retaincount exceeds 4. guard against this by periodically calling autorelease.


This account does not follow anyone
Loading...

Something went wrong.


Something went wrong.