On Sep 29, 2009, at 5:12 PM, Steve Cronin wrote:
This is the only method that Clang has an issue with…
Why does Clang believe that an 'owning retain count is expected' if
the method is never called?
Why is Clang picking on this one method which mirrors the mechanics
of so many others?
Clang-sa decides what the retain behavior should be based on the
method's name. Does the method name by any chance contain a substring
like "new" or "copy"?
There are some macros in some header or other which you can use to
tell Clang that a method should have some other behavior than what it
guesses from the name, although they aren't as flexible as I might like.
_______________________________________________
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
