Re: Code Completion & Nested Obj-C Messages: Wrong Scope
Re: Code Completion & Nested Obj-C Messages: Wrong Scope
- Subject: Re: Code Completion & Nested Obj-C Messages: Wrong Scope
- From: David Ewing <email@hidden>
- Date: Tue, 13 Jun 2006 10:06:22 -0600
On Jun 13, 2006, at 4:10 AM, Mason Mark wrote:
I don't have a solution, but have basically the same problem. I
don't get code-completion suggestions for NSArray or other
inappropriate classes, I just get "no completions found" all the time.
This is in basically any "real" project. That is to say, it doesn't
happen with little test projects but happens in every real project I
work on (say over a few dozen source files?). Rebuilding the index
doesn't affect this (although I do it often to fix other problems).
I assume in my case it's been this way for a long time, because I
have a bunch of text-expansion macros like:
NSUserDefaults *ud = [NSUserDefaults standardUserDefaults];
NSFileManager *fileManager = [NSFileManager defaultManager];
...and so forth, for exactly that reason.
Since in my experience "Code Sense" is pretty broken generally, I
have just chalked this up as a limitation. Since most of those type
of methods have a return type of "id", there is a huge number of
potential completions.
Although a simple heuristic to guess which methods might be
appropriate should work fine, I just have always assumed that Code
Sense doesn't have one and is simply baffled by the large number of
possibilities, so it silently gives up (which it seems to do in a
number of other situations also).
Your post made me wonder, though, since you say it works fine in
your other projects. Does it work even in reasonably-sized projects?
I had always assumed this was broken for everybody pretty much all
the time.
It's certainly not broken for most people most of the time. (Unless
people are very quiet on the matter - and that's not usually how it
works.) If you're seeing issues, please file bugs: <http://bugreport.apple.com
>.
We do know of some limitations, but we're very interested in hearing
any issues people are running into. We're especially interested if you
can send in a reproducible test case. (Well, that doesn't make us more
interested, but it does help us fix the bugs quicker!)
Dave
_______________________________________________
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