FROM : I. Savant
DATE : Sat May 17 02:21:43 2008
> Amen. One of the first things I do to any Xcode project I work on is
> turn on "Treat warnings as errors" in the build settings. For some
> reason almost all of Obj-C's type-checking errors appear as
> warnings, and you ignore those at your peril.
VERY good advice. A little self-discipline is good. I admit to
previously being very bad about "harmless" warnings. By harmless, I
mean the "may not respond to" variety. It's messy, though, and it
always rubbed my OCD wrong. ;-)
Hi. I'm Idiot Savant and I have a Warnings problem. I've been clean
for about a year now and it gets easier every day ...
< sits down, waits for clapping >
--
I.S.
DATE : Sat May 17 02:21:43 2008
> Amen. One of the first things I do to any Xcode project I work on is
> turn on "Treat warnings as errors" in the build settings. For some
> reason almost all of Obj-C's type-checking errors appear as
> warnings, and you ignore those at your peril.
VERY good advice. A little self-discipline is good. I admit to
previously being very bad about "harmless" warnings. By harmless, I
mean the "may not respond to" variety. It's messy, though, and it
always rubbed my OCD wrong. ;-)
Hi. I'm Idiot Savant and I have a Warnings problem. I've been clean
for about a year now and it gets easier every day ...
< sits down, waits for clapping >
--
I.S.






Cocoa mail archive

