RE: Faster indexing for batch find and project indexer
RE: Faster indexing for batch find and project indexer
- Subject: RE: Faster indexing for batch find and project indexer
- From: "Karan, Cem (Civ, ARL/CISD)" <email@hidden>
- Date: Thu, 16 Nov 2006 07:41:24 -0500
- Thread-topic: Faster indexing for batch find and project indexer
I think I was unclear before, and that is why we seem to be talking past
one another, rather than talking to one another. I'll try to explain my
particular situation...
First off, I'm not disagreeing with you. Given a choice, I would do
precisely what you are suggesting. The problem is that I don't know
WHERE these comments have been placed. Quite a bit of the time, various
people on my team put Doxygen comments into supplemental files (like
Python files, or LaTeX files, or random text files, or in some HTML
file, or... etc., etc. etc.) as a standard way of commenting (all of us
read Doxygen very well, so it is a convinient shorthand, even for files
that can't be parsed by Doxygen). However, different people have used
different styles of Doxygen comments. We've decided to standardize on a
single style, and, just to make it easier on all of us, I was told to
make the changes and commit them back to our repository. Since *I*
don't know which files to search in, the easiest way for me is to batch
find *all* the files.
If it were just me, and I knew which files had these comments, then I
could do precisely as you're suggesting.
As for the suffix tree solution, it is still a valid method of indexing
all possible search strings, and to do it in a manner that is both
compressed, and extremely rapid to search over. If the XCode team used
it as an index, then searching would be vastly improved. Note that
nothing I've mentioned says that search sets are a bad idea, or anything
like that; in fact, suffix trees can be combined with search sets fairly
easily to produce ultra-rapid searching. The only point I was
originally trying to make was that, properly used, suffix trees could be
extremely useful for searching through large numbers of files and data.
That's all.
Thanks,
Cem Karan
-----Original Message-----
From: James Bucanek [mailto:email@hidden]
Sent: Wednesday, November 15, 2006 6:17 PM
To: Karan, Cem (Civ, ARL/CISD)
Cc: email@hidden
Subject: RE: Faster indexing for batch find and project indexer
Karan, Cem (Civ, ARL/CISD) wrote on Wednesday, November 15, 2006:
>As for searching the source files, well, we have a little over 300 MB
>of source + supplemental files, all of which need to be searched
through.
>Normally, I would just select the files I was going to search over, and
>just search them, which would make the find much faster, but I can't in
>this case. That is why I'm taking a hit every time I search for
>something; I have to search across all of the files, yet again. By
>building an index as files are added to the project, and keeping it up
>to date as the files are changed (and by updating ONLY those parts that
>changed!) I figure that searching can be made faster.
As I alluded to in my earlier posting, I would suggest looking at
creating a find set[1] specifically for this work. If you problem is
that your searching a horde of files you don't need to be searching,
then the key is to limit the search. In a find set, the set of files to
be searched can be defined using multiple regular expressions. You might
be able to limit the searches to just the files of interest, without
having to manually select them or maintain a list of files by hand.
James
[1] Open the Project Find window and click on the Options... button. At
the top, create a new Find set and define the files that constitute that
set. Close the dialog, then select your custom set when performing
search/replace operations.
James Bucanek
____________________________________________________________________
Author of Beginning Xcode ISBN: 047175479X
<http://www.beginningxcode.com/>
_______________________________________________
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