30 Oct
2011
30 Oct
'11
4:25 p.m.
On 30/10/11 2:25 PM, Alexey Toptygin wrote:
On Sun, 30 Oct 2011, Toby Thain wrote:
It would be a straightforward vim or emacs extension (and there are
plenty of libraries that implement this - such as Lucene/Solr).
If IDEs are "heavyweight" or have no indexing short of grep (Eclipse
seems to grep), then that is, as I say, a perfect illustration of
heedless, unreasonable bloat.
--Toby
On 30/10/11 12:32 PM, Alexey Toptygin wrote:
Do you have any examples of software that does this sort of indexing
that's not built into a heavyweight IDE? I've never seen any. On Sun, 30 Oct 2011, Toby Thain wrote:
Yes, that problem is solved by RAM, and smarter indexing :)
In fact, it's a *perfect* illustration of how a fast machine can
conceal a very inefficient design! Grepping a source tree for an
identifier is orders of magnitude more wasteful than simply using an
inverted index. Are there common things that a programmer waits
for?
Grepping the source tree. If I substantially change the behavior of
function X, I need to be sure it won't break any of the (often hundreds
of) call sites. Enough RAM to fit the entire source tree in the cache is
very helpful for this, and that can mean several GB...
Alexey