There's no question that Objective-C variables are longer than those seen in most ANSI C source, but the idea is that you're better off wasting some space than allowing things to be ambiguous.
Out of all the source code I've looked at, I've had more success with getting meaning at a glance from ObjC stuff than anything else. This is due in no small part to the naming conventions.
As for private ivars, the suggestion is that you do something like DC_elementName or DC_contentsHint, using the same prefix as the class itself. Part of the reason for this to avoid collisions with ivars declared in super classes such as NSObject, NSProxy, or perhaps some of the magical runtime subclasses.
by Scott Stevenson — Dec 16
Out of all the source code I've looked at, I've had more success with getting meaning at a glance from ObjC stuff than anything else. This is due in no small part to the naming conventions.
As for private ivars, the suggestion is that you do something like DC_elementName or DC_contentsHint, using the same prefix as the class itself. Part of the reason for this to avoid collisions with ivars declared in super classes such as NSObject, NSProxy, or perhaps some of the magical runtime subclasses.