On Thu, Jun 5, 2008 at 11:50 AM, Dale Jensen <[EMAIL PROTECTED]> wrote: > This may be an Xcode question, rather than Cocoa, but it relates more to the > language, so I'll ask here. > > 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.)
Have you remembered to #import <Cocoa/Cocoa.h>? What does your project's prefix header look like, if any? Are you linking with -framework AppKit? --Kyle Sluder _______________________________________________ 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 [EMAIL PROTECTED]
