On Aug 30, 2008, at 9:31 PM, Jon Davis wrote:
So do no-ops exist solely for the sake of being there for convention, i.e. "do this if you're implemented, ignore if not"?
In this case, that's what it's being used for. Initially (back when we coded in assembly language,) NOP was most often used for timing and aligning memory. Additionally, if you had to modify a live binary without source (legitimately, think Y2K,) NOPs can be used to modify the code directly without fluxoring up the jump tables.
I'm not sure that a NOP would actually show up in the resultant code of a NSAutoReleasePool call, I guess the compiler could substitute it, but it could also make the call and return nothing with the same result. Or just skip the line altogether. The documentation may be just using an old, but conventional, term, to let you know that nothing would happen.
dale -- Dale Jensen, CEO Ntractive, LLC [EMAIL PROTECTED] http://www.ntractive.com _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [EMAIL PROTECTED]
