On May 8, 2010, at 12:35 PM, James Bucanek wrote: > Kyle Sluder <mailto:kyle.slu...@gmail.com> wrote (Saturday, May 8, 2010 8:48 > AM -0700): > >> It might produce less code, it might not. If you're operating at the ObjC >> level of abstraction and worrying about the codegen of self=[super init], >> your >> priorities are out of order. > > I'm a coding genius. My priorities are never out of order. ;) > > There are completely legitimate reasons to want to optimize one's code, and > examining the overhead of -init seems perfectly rational to me. This seemed > to be the brunt of the original poster's question. > > I was simply pointing out the fallacy of believing that if ((self=[super > init])!=nil) is inherently less efficient (e.g. produces more code) than if > ([super init]!=nil).
Those two produce different results, so comparing their efficiencies is pointless. To make matters worse, "if ([super init] != nil)" is also wrong, so it doesn't matter if it is more efficient. Glenn Andreas gandr...@gandreas.com The most merciful thing in the world ... is the inability of the human mind to correlate all its contents - HPL _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
