FROM : Kyle Sluder
DATE : Thu Jul 03 19:47:39 2008
On Thu, Jul 3, 2008 at 12:40 PM, Chris Paveglio
<<email_removed>> 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.
What type did you declare theSettings to be?
> 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?
Many (dare I say most?) developers consider warnings to be the
equivalent of the compiler vomiting in its mouth -- errors are the
subsequent suffocation. Perhaps you can tell how strongly I feel
about this.
--Kyle Sluder
DATE : Thu Jul 03 19:47:39 2008
On Thu, Jul 3, 2008 at 12:40 PM, Chris Paveglio
<<email_removed>> 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.
What type did you declare theSettings to be?
> 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?
Many (dare I say most?) developers consider warnings to be the
equivalent of the compiler vomiting in its mouth -- errors are the
subsequent suffocation. Perhaps you can tell how strongly I feel
about this.
--Kyle Sluder






Cocoa mail archive

