On Wed, Sep 23, 2009 at 6:24 AM, Kirk Kerekes <[email protected]> wrote:
> ... If you don't happen to be using any of these, (or any macros that hide > relevant code, because the analyzer appears to operate only on unexpanded > code) you should be golden. The analyzer definitely expands macros. I've got some legacy code at work that's got a frequently-used macro that can basically return from the method at any point, and it's producing ALL sorts of memory leak warnings. _______________________________________________ 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]
