Re: Does this caution need fixed? (newb)

FROM : Andy Lee
DATE : Thu Jul 03 19:35:55 2008

You're assigning a value to theSettings.  That's what the "assignment" 
in the warning message refers to.  What is theSettings declared as?

You should fix your code so that all warnings go away.  Warnings 
almost always indicate that something could potentially go wrong, so 
you might as well take away that possibility.  Also, if you ignore 
warnings you think it's safe to ignore, you may not notice when an 
important warning appears.  When I upgraded to Xcode 3, I got a whole 
bunch of probably harmless warnings, but I fixed them all for this 
reason.

That said, some people have different ideas about what the compiler 
should warn you about, and set their build settings accordingly.

--Andy


On Jul 3, 2008, at 12:40 PM, Chris Paveglio wrote:

> I have a loop that gets the user's home directory, and then adds a 
> string to complete the file path for several files.
>
> This line:
> theSettings = [NSHomeDirectory() stringByAppendingPathComponent:
> [myPrefs objectAtIndex:i]];
>
> gives me a caution sign when I compile. It says "assignment from 
> distinct Objective C type", but the code works.
> How important is it to fix that? Also, should my code be "caution 
> free" as a sign of clean coding or can some cautions that don't 
> affect functionality be dismissed?
>
> Thanks,
> Chris
> Cocoa Newb, Applescript Vet
>
>
>
>
> _______________________________________________
>
> Cocoa-dev mailing list (<email_removed>)
>
> 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/<email_removed>
>
> This email sent to <email_removed>