Re: misspelled methods
Re: misspelled methods
- Subject: Re: misspelled methods
- From: Dennis Munsie <email@hidden>
- Date: Tue, 18 Aug 2009 15:42:03 -0400
Please file a radar on this - I'll file one too. I've certainly spent
quite a bit of time on these kinds of errors and I would happily turn
on the warning for this if it existed.
dennis
On Aug 18, 2009, at 12:45 PM, Todd Heberlein <email@hidden>
wrote:
That would catch some typos, but wouldn't have helped Todd since he
probably never sends the viewDidLoad method himself.
That is correct. I was overloading (or trying to) the
UIViewController's -viewDidLoad method which would be called behind
the scenes. There were no compiler warnings or runtime warnings. My
code simply was never called.
I was just thinking that if in your @implementation block you
implement a method:
- (void)someMethodName
that is not declared in either your class's interface or the
interface of any parent class, then a compiler warning could be
issued.
Another thing that might help would be for auto-completion to be
smarter while you're entering a method declaration. (Weird -- I
just entered "- (NSString *)descriptio" and -description was not
offered as a possible completion. Will file a Radar.)
Yes, that would help. That has bugged me a bit, but Xcode has made
so many improvements over the years I really can't complain too
much. I probably type only a fraction of what I used to type.
Todd
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden