Re: Accessing function definitions
Re: Accessing function definitions
- Subject: Re: Accessing function definitions
- From: Laurence Harris <email@hidden>
- Date: Wed, 25 Oct 2006 21:34:33 -0400
On Oct 25, 2006, at 7:49 PM, Chris Espinosa wrote:
On Oct 25, 2006, at 9:13 AM, Laurence Harris wrote:
When I Command-double-click a function name, Xcode takes me to the
definition of that function if there is only one function with
that name, or it pops up a menu containing the various definitions
if there are more than one. This is fine, as long as there aren't
more than 20 such functions. If there are more, the menu seems to
list a maximum of 20 and adds a Find More item, which initiates a
search using the Find window. Obviously the usefulness/convenience
of this drops by an order of magnitude if the one you want isn't
in the first 20, and I won't even go into the issues involved in
using Xcode's Find. So...
- Is there any way to increase the number of items that will
appear in that menu before the Find More option is added?
- Ideally can I increase it to like, a thousand?
- Is there any way to get a simple list of them a la CodeWarrior
instead of one of those two-line-per-item lists Xcode seems to
like to produce?
Do you really want to pick from a list of a thousand items?
Assuming I actually had that many instances of a function, how does
the current Xcode mechanism spare me from doing that? As far as I can
tell, Find More produces a Find window with a list of all of the
desired functions. It's just a lot more tedious and less intuitive to
navigate that list that it is to traverse a popup menu of functions.
Or do you want a shorter and more correct/appropriate list?
I don't understand why these are the only two choices. If I Option-
double-click a function name in CodeWarrior, CW produces a list with
one function/line, and they look like:
CSomeWindow::HandleHICommand
If I open a CM, I get a submenu with all occurrences, listed by
*class*, not by file (see another post for why I prefer the class
references). Have you spent much time in CW? Did you find that
mechanism to be problematic?
That is, if you have a very common member function that's in every
class in your project, do you really want a list of every member
function of every class with that name,
Well, at this point I don't have any functions with a thousand
implementations. Is this common?
or do you want a better way to navigate to that member function in
a specific class?
I want a better way for the typical developer to work efficiently,
and complex mechanisms designed to address extreme needs at the
expense of simple, easy to use mechanisms that work well 99% of the
time don't really make sense to me. In all honesty, what percentage
of Mac developers do you believe work regularly with projects in
which there are large numbers of functions with a thousand
implementations? Or is Xcode designed for people writing operating
systems and the rest of us schmucks just have to suck it up and deal
with all this complexity?
In any case, Xcode actually does what I want if there are no more
than 20 instances of a function, but let's face it, 20 is a pretty
lame cutoff number for that. Now, if you increase that to 200 or 300
(or whatever point imposes a significant performance hit), I suspect
that would take care of 99.8% of most people's needs for quick
access, and then the few people who have a thousand instances of a
function can struggle with the complex way. FWIW, I think I'd rather
wait for a menu with a thousand items in it and navigate it than have
to open a separate window and navigate a list with a thousand entries
in it.
Larry
_______________________________________________
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