That was my thought too. You mention that your CFAString is an NSObject subclass but do not mention what your other class is.
On a similar note, you might want to reconsider the name of CFAString. As you are probably aware, Core Foundation classes are prefixed with CF, and there is even a CFString class. "CFAString" seems, at best, likely to be hard to see visually or, at worst, potentially conflict with a future public or private Core Foundation class. -- Conrad Shultz www.synthetiqsolutions.com On Jan 29, 2011, at 8:25, Scott Ribe <scott_r...@elevated-dev.com> wrote: > On Jan 29, 2011, at 8:29 AM, Travis Kirton wrote: > >> warning: incompatible Objective-C types 'struct CFAString *', expected >> 'struct NSString *' when passing argument 1 of 'initWithString:' from >> distinct Objective-C type > > The frameworks contain plenty of initWithString: (NSString*) declarations. > You might want to use a name that is more specific. _______________________________________________ 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
