Re: Accessing function definitions
Re: Accessing function definitions
- Subject: Re: Accessing function definitions
- From: Laurence Harris <email@hidden>
- Date: Wed, 25 Oct 2006 21:28:10 -0400
On Oct 25, 2006, at 7:42 PM, Shawn Erickson wrote:
Yeah correct (think Fritz was thinking it would popup a window other
then the one it does) but if you expand the project window and click
once on "Project Symbols" you can type in the search field in the
upper right corner and get a live filtered list based on what you are
typing.
You can also bring up this view by selecting View->Show->Symbols (you
can attach a key equivalent to this if you want).
I should also note that you can select a find result in the Group &
Files listing and see a flatter tabular listing of the find result.
I want to be able to do this without involving the Find window at
all. In any case, I find that list of functions to be tedious to use.
In some cases what I see is a column of entries that all say
"Instance method: OSStatus" and another column of files where they
occur (see my comment below about not thinking in terms of files).
Here's a typical scenario:
Let's say I'm looking a member function in my CSomeWindow class and
see that HandleHICommand is called from that function.
HandleHICommand is a virtual function in my base window class that's
overridden in most of my window classes, so there are definitely more
than 20 of them. I want to jump to the one that's being called from
the function I'm viewing, which is most likely
CSomeWindow::HandleHICommand. Note that the operative phrase there is
"jump to," not "slog my way to." In CW I can open a contextual menu
with a submenu that lists every instance of this function. I just
look down until I find CSomeWindow::HandleHICommand, select it and
I'm there.
Note that I think of all this terms of the class structure, not the
files containing the functions. So I'm looking for
CSomeWindow::HandleHICommand, not the instance of HandleHICommand
that's located in a particular file. Unfortunately Xcode is very file
and path oriented. Just speaking for myself, I don't really
understand that obsession. I think it terms of program structure, not
files and paths. For example, if CSomeWindow is a simple subclass of
CWindow, I might put all of its function definitions in a file named
CSomeWindow.cpp. If it's not so simple, I will put functions related
to Carbon Events in a file named CSomeWindow_CE.cpp. Whatever the
name of the file, all I care about is going to the definition of
CSomeWindow::HandleHICommand and I want to do it as simply and
directly as possible so I can get work done. I don't get paid by the
hour or even the month, I get paid by work accomplished. That means
that every time it takes me 10 times as long to do something in Xcode
as it did in CW, it costs me money.
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