anchor.diff:  %% refactoring changes the filename as well. </li>
   %% </p>
   %% =====================================================================
  -%% @spec rename_mod(FileName::filename(), NewName::string(), SearchPaths::[string()])-> term()
  +%% @spec rename_mod(FileName::filename(), NewName::string(), SearchPaths::[dir()])-> term()
   %%   
   rename_mod(FileName, NewName, SearchPaths) ->
       refac_rename_mod:rename_mod(FileName, NewName, SearchPaths).
   
  -
  +%%@private
  +%% @spec rename_mod_eclipse(FileName::filename(), NewName::string(), SearchPaths::[dir()])-> term()
   rename_mod_eclipse(FileName, NewName, SearchPaths) ->
       refac_rename_mod:rename_mod_eclipse(FileName, NewName, SearchPaths).
   
  
positive.code: 
  %% =====================================================================================
  %% @doc The duplicated code detector that works with multiple Erlang modules.
  %% <p> This is the duplicated code detector that works with multiple Erlang modules, which should be used from 
  %% the command line.</p>
  %% <p> This function only reports the found duplicated code fragments. It does not remove them.
  %% The user have to  will supply three parameters: the lists of Erlang files to check,  the minimum number of 
  %% tokens the a code clone should have, and the minimum number of the times a code fragment has been 
  %% duplicated.
  %% </p>
  %% <p> The current version of the duplicated code detector can report clones that are syntactically 
  %% identical after consistent variable renaming, except for variations in literals, layout and comments.
  %% </p>
  %%======================================================================================
  %% @spec duplicated_code_in_dirs(FileNameList::[filename()], MinToks::integer(), MinClones::integer()) -> term()
  
  duplicated_code_in_dirs(FileNameList, MinToks, MinClones) ->
      refac_duplicated_code:duplicated_code(FileNameList, MinToks, MinClones).
      
  
  %% ==================================================================================================
  %% @doc Search for clones of a user-selected expression/expression sequence in the current file.
  %% 
  %% <p> This functionality allows to search for clones of a selected expression or expression 
  %% sequence.  The found clones are syntactically identical to the user-selected code fragment after consistent variable 
  %% renaming, except for variations in literals, layout and comments. 
  %% </p>
  %% <p> When the selected code contains multiple, but non-continuous sequence of, expressions, the first
  %% continuous sequence of expressions is taken as the user-selected expression. A continuous sequence of
  
negative.code: %% should not be already in scope (either defined or imported) in that module. </li>
  %% </p>
  %% ========================================================================================
  %% @spec tuple_funpar(FileName::filename(), Line::integer(), Col::integer(), Number::string(), SearchPaths::[dir()])
  %% -> term()
  tuple_funpar(FileName, Line, Col, Number, SearchPaths) ->
      ref_tuple:tuple_funpar(FileName, Line, Col, list_to_integer(Number), SearchPaths).
  
  
  %%@private
  %% @spec tuple_funpar_eclipse(FileName::filename(), Line::integer(), Col::integer(), Number::string(), SearchPaths::[dir()]) -> term()
  tuple_funpar_eclipse(FileName, Line, Col, Number, SearchPaths) ->
      ref_tuple:tuple_funpar_eclipse(FileName, Line, Col, list_to_integer(Number), SearchPaths).
  
  
  %%=========================================================================================
  %% @doc From tuple to record representation.
  %% <p> To apply this refactoring mark the tuple in the editor, which is a function 
  %% parameter or an application argument.
  %% Then select <em> From Tuple To Record </em> from the <em> Refactor </em> menu, 
  