Re: Finding unused code with in a project.

On Thu, 29 May 2008 23:28:03 +0100, Nicholas Ring <Nicholas.Ring@xxxxxxxxxx> wrote:
I think his aim is to make the source files smaller (and probably less
cluttered), not the executable(s).

That is correct Dave & Lucian. In one application there is, I believe,
a lot of code that is has been disable (ie, no path to it) but not
removed and there is a number of us think it is time to remove this
code (which will be donated to the 'obsolete' directory, just in case
it is required in the future...).

That was my initial thought too - and for me the major time saving would be /not/ having to refactor obsolete methods which have been affected by some lower-level change.

But a compiler can only tell whether a method is not used within the /current/ project. It cannot say that it is not called by some other project which might also "use" that unit.

You could use a source file searching utility like AgentRansack http://www.mythicsoft.com/agentransack/ - perhaps using the absence of the "blue dots" to suggest likely candidates for unused methods.

--
Paul Scott
Information Management Systems
Macclesfield, UK.
.