Date: Tue, 13 Oct 1998 18:13:42 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: George Foot <george DOT foot AT merton DOT oxford DOT ac DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: Math library source code
In-Reply-To: <Pine.OSF.4.05.9810091521500.23422-100000@sable.ox.ac.uk>
Message-ID: <Pine.SUN.3.91.981013181320.4278Z-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


On Fri, 9 Oct 1998, George Foot wrote:

> Basically, browse around until you find what you're looking for.  
> Something like `grep' is very helpful here -- or even "dir /s
> sqrt*.c" or using djgpp builds of fileutils "ls .../sqrt*.c".
> Also note that some editors (Emacs?) have the facility to scan a
> directory tree for function definitions, and remember exactly
> which file defines which function, allowing you to later look up
> functions just by typing their names.

Actually, the best tool for this job is GNU ID-utils
(v2gnu/idu32b.zip).  They are like Grep, but they work by making a
database of tokens in the directory hierarchy, and then search that
database.  Since library sources seldom change, you can make the
database once, and then searches are lightning-fast.  Also, the
tokenizer is source language sensitive, so it gets the job done with
less clutter than Grep.  And of course there's an Emacs interface ;-).