Re: Getting rid of specific "May not respond" messages
Re: Getting rid of specific "May not respond" messages
- Subject: Re: Getting rid of specific "May not respond" messages
- From: j o a r <email@hidden>
- Date: Thu, 5 Jun 2008 09:11:25 -0700
On Jun 5, 2008, at 8:50 AM, Dale Jensen wrote:
In my project, I get a number of warnings that are invalid, telling
me that something or another "may not respond" to something, when in
fact, it can. As an example, I get a lot of these:
warning: 'NSString' may not respond to '-
stringByReplacingOccurrencesOfString:withString:'
warning: 'NSFileManager' may not respond to '-removeItemAtPath:error:'
warning: 'WebView' may not respond to '-mainFrameURL'
while are all Cocoa framework calls, which do work. In some
instances, I've found that tracking down a header file and
#importing it sometimes gets rid of the message, but not always
(can't seem to get rid of the three shown here, ever.)
These are all methods added in Mac OS X 10.5. Check the SDK settings
for your target.
j o a r
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden