The most clever strategy I have seen was also based on version-control – MS Source Safe – and it worked by analyzing the deltas. It looked for references to a subroutine-name within the blocks of changed text. It also examined the human comments which accompanied each revision ... what the developer said about it ... and the number of times a particular block of source code was changed within a small amount of time. There was some "smarts" about calculating how a particular line-number might have changed due to insertions and deletions that surrounded it. But this code was all being done in-house (by the developers at one cell-phone company that had acquired another one), and I never knew of anything to be released.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link
or How to display code and escape characters
are good places to start.