Hi,
Look at this code:
myUserInfo = [self.pUserIDDict objectForKey: theUserInfo.pUserID];
if (myUserInfo != nil)
{
LTWAssertAlways(@"myUserInfo - Dupe ID!!!!!!!!!!");
}
if (theUserInfo.pUserID != nil)
//Remove this Line for Warning
[self.pUserIDDict setObject: theUserInfo forKey: theUserInfo.pUserID];
//Warning on this line!
}
I get a warning saying that Key argument for setObjectForKey cannot be nil? I
am wondering why it suddenly started moaning about this here and not other
places were it is used and could be nil, like this:
myUserInfo = [self.pUserIDDict objectForKey: theUserInfo.pUserID];
This is the only place I’ve seen this warning and I’m using keys that could be
nil in lots of places (without any problems as I obviously make sure that I
don’t pass a nil…..
All the Best
Dave
_______________________________________________
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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
